To circumvent this rate limit, one could add a specific hostname for that specific host (e.g. host42.amsterdam.nl.example.com or whatever). And you'd have the ID for the server of that certificate automatically! Win-win.
Agree that would be one way to deal with it. But if they really have that many server instances using the same cert names they would be better off acquiring the cert in a dedicated instance and distributing it as already suggested by @bruncsak