To answer this a bit more directly than the others:
-
LetsEncrypt removed the TLS-SNI-01 ACME Challenge Mechanism in 2019 because it was insecure and could lead to the mis-issuance of tickets, especially in shared hosting scenarios. see March 13, 2019: End-of-Life for All TLS-SNI-01 Validation Support
-
As @Maxh stated, you can use the TLS-ALPN-01 challenge to verify over HTTPS - however it is a technically more advanced challenge for webservers to implement, and therefore most webservers do not, or can not, support it.
Because of those two situations, there is essentially zero chance of a more accessible HTTPS verification challenge in the foreseeable future. Everyone supports the idea, but there are technical and security restraints that are preventing it from happening in a method other than TLS-APLN-01.
If your concerns are over having to manage another service and you do not want to run port 80 all the time, you can use the pre/post hooks in certbot - or other clients - to only turn on Port80 during the ACME process. You can also choose to have Certbot handle the port80 responses via the included "standalone" option, proxy that traffic to your https server, or serve a redirect to your https server.