If you want to step up and be the maintainer of one or more of these modules in the standard library, I'm pretty sure you would be welcomed. PEP 594 is basically just a formalisation of the fact that no one has volunteered to do this yet.
Also. If maintenance of aging modules becomes tiresome, maybe it is a strong hint to keep backwards compatibility in Python proper.
Or.. or, just consider that the community looked at the relevant trade offs and decided what it decided.
If someone wants an old built-in module they can use an old python version.
Core language backwards compatibility is a non-issue. Approximately zero percent of maintenance costs go towards that.
I'm reminded of the Hitchhiker's Guide to the Galaxy:
"It was on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying ‘Beware of the Leopard."
https://discuss.python.org/t/pep-594-removing-dead-batteries...
someone did volunteer to maintain cgi and cgitb.
But nonetheless those modules remained listed in the PEP.