I think the implication is if there is a security breech at their end, someone could hijack the service to point IPv6 addresses to somewhere unexpected.
If it's only used in development, it's not too big a deal, but could still be use to compromise things.
Maybe that's restriction for LetsEncrypt (I haven't used it myself) but certificates aren't restricted to 2nd level.
No, this is nothing specific for Lets Encrypt, this is how PKI works.
A certificate is for a domain name, not an IP address.
Anyone can point a (sub)domain that they own to an IP address that they do not own. And then get a valid certificate for that domain.
I can point an A record to [your-ip].[my-domain] and I will be able to get a valid cert for that address. However, the address in your address bar will still point to [my-domain], not yours.
The domain name will still be 'has-a.name', so I don't understand how the certificate part is supposed to work. If anything you'd have to get their TLS cert for this to work, not the other way around.