ohaodha
The keybindings aren't mentioned in the "Why?" section of this blog post, and clearly aren't the point of the post. You can get extensions to add Emacs bindings to full-featured browsers, and there's even the Nyxt browser which has Emacs keybinds and Lisp configuration.
The core reason listed in this blogpost for browsing this way is the very fact that it is less featureful and less convenient. As someone who uses Emacs, I know that eww isn't as convenient as a fully-fledged web browser and I know that sometimes the hard way of doing things can be beneficial. I found this blog post disappointing because it doesn't afford you any new information, nor tell anyone about any actually useful features about browsing in eww.
I think the idea that you do something in a more difficult or less convenient manner for the sake of "mindfulness" or "focus" is well-established, and what I hope for (and am always disappointed by the lack of) when reading such blog posts is an actually useful feature of the unconventional method in question.
The title of this blog post promises some usefulness from using Emacs as your browser, and upon reading, you discover that the "usefulness" is the inconvenience and impracticality of using it that way.
A 'bananas' order for 5000 obscure book titles fuels suspicion
Obviously, there should be URL protection rules to control what it can access, but this requires a very specific and unlikely set of circumstances to exploit.
Building an Affiliation Network for Blog Posts and Tags in Hugo
Fretboard Memorisation with Modular Arithmetic
It works on plaintext, but you can define pre-processing hooks to convert, e.g., a PDF or webpage into readable content using the config file.