I've read the book "Scrum: The Art of Doing Twice the Work in Half the Time" by Jeff Sutherland and J.J. Sutherland which goes into the history of how Scrum was invented, and the ideas and philosophy behind it - and neither that quote of yours, nor anything similar to it, is represented in that book.

I've also read "Essential Scrum" by Kenneth S. Rubin, which many consider the best book to read on Scrum, and that does not endorse anything like your quote either. That book definitely is more on the "all-you-can-eat buffet" side of things.

Both books clearly state in some form or other, that ALL processes cause overhead - and that does include the processes suggested/recommended by Scrum. And that's why you should always use as little processes as possible. Sadly you can't work without any processes at all - if you try that, some informal processes will just emerge on their own. It just doesn't work without - unless you are a tiny team of friends.

Scrum has become a big commercial enterprise, that wants to sell courses and trainings and scrum master certificates. They have a financial incentive to churn out rules to follow, because that's how they earn money. But that's surely not what is best for teams and work motivation. I really don't think that Scrum originally was about rules at all - it was (and should be) about what is best for teams and work motivation. Just my 2 cents.