You seem to think that DNS names being exposed in TLS negotiation was an accident.
The purpose of DNS names being exposed by the SNI extension is to facilitate name-based virtual hosting. It is not to expose additional information to 3rd parties sniffing the line; that part was clearly an accident.
It can be fixed, and I see no reason why it won't be.
There are legitimate reasons for some people being able to selectively block web traffic
If someone's abusing SNI information for censorship purposes, then that's yet another reason this needs to be fixed. No a 3rd party sniffing to identify names and tampering with or "blocking" SSL traffic is not legitimate, for any reason.
being exchanged to become opaque those who want/need to block will do so using other means like IP blocks/reverse DNS lookups
One protocol at a time. There are other undergoing projects within the industry to privacy-secure DNS, so 3rd parties won't be able to intercept your DNS requests or figure out what DNS names you are looking up.
As for IP blocks, there are always methods available of proxying traffic, including ToR... these could even get built into standard web browsers as a "fallback" connection method, if for some reason, a direct connection was failing, or in due course using default proxying, for additional source IP privacy shielding.
New proxies are becoming available every day, so the major browsers just need to incorporate all available anti-censorship techniques, to ensure that network-based traffic tampering/interception won't work out of the box.