Actually, I think that this new policy is a great incentive to go v1.x.y
IMO, the off-by-one semVer is (was for me) a big annoyance. See, according to it in the v0.x.y stage raising x means a breaking change. So, either bug fixes or new features have to be accommodated in changing y. Sorry, but this is a complete nonsense to me, and I never followed it (and bet I’m not alooooone)
Now, with the new policy, this semVer strictness will be enforced to everyone. So all those (like me) that increase x for new features will be very annoyed with automatic refusals because they are not logging the breaking changes … but they are none because they were really nor following semVer here.
But life will be much easier on a v>=1.x.y world where breaking changes are real breaking changes (increasing MAJOR number) and new features are peacefully landing in x increases.