Yes, but I don’t see any reason to do anything like that. I’ve long wanted to move the “database” away from the forum, so that there’s a “proxy” running on a server that queries the forum regularly and then serves the OH clients. But, I’ve had no luck getting anybody to “help me” figure out how that would have to look. I don’t know the infrastructure, and what would and wouldn’t work.
But, to make a “break” is unnecessary - new clients can point to the new address, while old clients keep fetching directly from the forum. As older clients get fewer, the load on the forum subsides. It would be very bad to break the marketplace for older versions. I run 4.2.3 myself, I wouldn’t bother to host add-ons on the marketplace if I couldn’t use them. The whole point of all this, is to not break everything for those that doesn’t run the latest version.
I don’t see any point in making this “break” because you think that the version range is “bad” though. I think it’s fine as it is, only a bit bugged. But, there are many other shortcomings, so I have “made” another system that allows specifying more information.
If you look at this add-on, it’s the one I’ve used when developing support for versioning:
It allows specifying multiple versions of the same add-on, specify that an add-on depends on other add-ons, specify informration that you can’t today (documentation, issue tracker etc) - all this without breaking compatibility with the existing format.