The point of that statement was to run counter to the standards of "always us X type of comments" that some teams adopt. My suggestion is that there isn't a "correct" type of comment that you should always use, but rather that it's highly situational.
It's really a parallel to grammar in any other kind of language - there isn't a singular 'correct' way to structure a piece of writing into paragraphs, but it's also typically incorrect to treat each sentence as a paragraph or to avoid paragraphs entirely and write everything as a single block of text.
It's unthinkable that a team of writers would ever try to standardise on "never use paragraphs" or "every line is a paragraph", but some programming teams do exactly the equivalent of that!
The problem you described is real, and one I face daily at work. Anecdotally, every time we've tried to curate the comments and organize them (especially when referencing external documentation, as you also mentioned), it invariably ends up becoming stale and just another point of contention down the road.
I'm now more of a proponent of either not commenting, or putting the context and rationale in the commit message instead.