Seems like an interesting idea. The advantage of using Default Organization view in this context seems to be no overhead to publish/promote when a repo is synced. We could introduce some sort of automation to do the same for content views.
We have something similar for composite content views where the component CV can be set to “Latest version” and a new version of component CV automatically publishes the composite. Default org view works similarly in that it always points to latest version of a repository. We could set up other CVs to follow the same behavior.