3. userChrome.css is poorly documented but a nice option, not sure if Chrome has something similar. I have firefox set so that each tab is just a favicon and an extra pixel on each side. It mostly works well, except at some point the audio icon started appearing (it didn't when I first made the change) and it appears over the next tab, that makes it impossible or nearly impossible to directly select the next tab.
5. Reader mode is exellent if you use a more comprehensive javascript blocker, since many pages work in reader mode that wouldn't otherwise. Hopefully this isn't because it is actually running some javascript in reader mode or otherwise avoiding the usual blocking rules.
I think the reason there is a focus on "firefox is better than crome in some fundamental ways" is that once you get down to individual features they both change frequently and a feature that one person likes might really annoy someone else. The reasons to avoid chrome are not likely to change unless firefox gets as bad as chrome. If you convince someone to switch for some random feature then there is a much better chance they will switch back in a few releases when the random feature breaks in some way. Additionally, it isn't clear that firefox has an opportunity to convince all that many end users.
That being said, anyone who wants to do a feature comparison should go ahead and do it. The article seems to be saying "the real problem here is that other people are writing about the differences they care about".