I was not implying this. And sure, you may have a simple API where this doesn’t happen. But all the discussion there is about this topic may point out that versioning is not such a simple issue. If 99% of APIs handle this successfully as your research points out, then I think that would mean that one way is the absolute correct way and people just don’t have these issues.
Personally, I think people underestimate the entire problem of versioning. Take NPM as an example. It is widely used, didn’t take versioning seriously for a long time, and is still incredibly successful. So don’t let that stop you from using it. But if you are building an API you want to last for a long time, and evolve, ignore proper versioning at your own peril.