"by divorcing interface from information, Gopher sites stand and shine on the strength of their content and not the glitz of their bling."
Forcing content creators to focus on the strength of their content is pretty much a non-starter for most modern commercial enterprises. Which is why it's amazingly useful, but likely futile.
However - those who enjoyed text + links were left behind. I really just wanted text with some links. Thinking about setting up my own websites as a gopher site, just don't know the best ways to proxy it back to HTTP best.
I think pocket, instapaper, readability etc were all essentially peeks into a style of web we could have had where content presentation was something a user has decent control over.
Someone wrote up their experience using Lynx on the web around 2012.  Conclusion: "Not all the sites are usable with Lynx, but many of them offer at least basic functionality using the text-only web browser."
As long as there's HTML output, a more humane web browser could allow better customization of the information; it could infer the usual human organizational methods; lists, metrics, groupings, buttons, etc, and present it with your favorite background color, font size, line-length, image size, videos, etc, based on the hierarchical structure. The other camp is web apps, which is a different use case.
I'm not sure why this can't be done with HTTP? I have a Neocities page which is nothing but text and links with a barely-formatted page to be slightly-better-than-default.
Examples (NSFW language as obvious from the URL's but otherwise SFW):
(Note: Above two examples aren't my sites.)
"On the Web, even if such a group of confederated webmasters existed, it requires their active and willful participation to maintain such a hierarchical style and the seamlessness of that joint interface breaks down abruptly as soon as one leaves for another page. Within Gopherspace, all Gophers work the same way and all Gophers organize themselves around similar menus and interface conceits. It is not only easy and fast to create gopher content in this structured and organized way, it is mandatory by its nature. Resulting from this mandate is the ability for users to navigate every Gopher installation in the same way they navigated the one they came from, and the next one they will go to."
Simply put, it can't reasonably be done with HTTP/HTML because it requires active management (which as I pointed out is basically a non-starter), instead of being 'baked in' like it is with Gopher.
Since the announce of Webassembly, I have a scenario in mind. As you say, the VM can become a complete hypervisor that can can run a full OS. At that point, the browser will become useless and we could get rid of all the complexity of CSS and HTML and close that episode of internet.
Another point is for AI and robots, beautiful design is not a priority.
And worry about it deleting your root file system (https://github.com/MrMEEE/bumblebee-Old-and-abbandoned/commi...).
I agree with your points, but we should remember why the web got so popular: a safe, seamless software distribution mechanism. Recent OS's have approached this. (https://xkcd.com/1367/)
It can also be a tool for programmers or geeks (like markdown). It's more a niche.