I don’t think this is the problem.
1) The problem is that most people don’t understand what Scrum is really about. They take the mechanical Scrum view which is wrong and fail to see that scrum is a framework to help improve things.
2) Scrum defines “what” to do and NOT how to do it.
I personally feel the guide is badly written and encourages a mechancial view of Scrum. I also feel that the way it is written will add to the confusion of when or when not to use it. In the current state, adding this will likely add incorrect views of when not to use Scrum.
In communities, I often see people comment on when not to use Scrum. Most or wrong as they have a flawed understanding of Scrum.
My vote is to fix the wording of Scrum.