There is no best practice for this, of which I'm aware. I know of no command line option to specify a super POM, for example.
The only way I can think of seems even more risk prone and less convenient than specifying a parent explicitly, and I would not recommend it. You could check out the source code for Maven, and replace the super POM in the Maven model with your own, basically making a custom Maven build for your company. Then, you'd have to force all your developers to use the customized Maven version, which is just as inconvenient and risk prone as what you're trying to avoid in my opinion.
My company has a suite of corporate parent POMs, all extending from our own super POM. We've used this structure for years and years without issue.