The attacker who buys a bunch of domains and legitimately owns them for a period of time wouldn't have any issue getting SSL certificates for them.
Correct, but, even if not explicitly said, the cached entries should be associated to the certificate's fingerprint and immediately discarded once the certificate expires or is changed.
Certificates often change for legitimate reasons, e.g. Let's Encrypt certificates which must be changed every 3 months.
Another solution would be to use an unpredictable versioning scheme so the attacker can't anticipate the name of the resources.