What we really need form Lets Encrypt is stability and lack of change. But LE is just following the megacorps down the current TLS road. We're already down to only 30 day certs and on the second iteration of acme. Acme original protocol setups no longer work, they were broken by the dropping of support.

Addding new methods of validation does not help nearly so much as just supporting existing methods for more than a few years would. The race to the bottom will end up with an incredibly fragile system that breaks the moment automation does. Combine this with the trend towards HTTP-only and any given website will only have a lifetime of a couple years without direct human intervention. This is a drastic change from the status quo of websites simply lasting forever and being accessible till their webservers stop.

It is 100% a corporate-for-profit-only mindset and architecture. LE is not designing or accomidating human person goals and needs.

You can set up a script that installs an updated web server next to the old one, tests it and switches the site to the new version. Run it on a timer every week or so. If any tests fail it either sends a message to you or tells a coding agent to fix it.

It's practically zero overhead, low maintenance (most updates are not breaking) and you get the latest version of everything. If you're worried about supply chain attacks set a minimum release age.