Using semver is a promise that if you make a backwards-incompatible change you will update the major version.

That's entirely separate from any promise, or statement of intent, that you might want to make about whether you're hoping to make backwards-incompatible changes rarely or frequently.

Teaching people that they should consider incrementing the major version as indicating a failure isn't going to be helpful.

In practice, given the way semver is defined, if this idea catches on I fear the main effect will be to increase the number of projects that never choose to declare they're version 1.0.