It’s possible, but I wouldn’t advise it in a plugin. Assumptions about the path structure are found across various places in the codebase, and other customisations (plugins and themes) for that matter. You could build something that would address all of those instances now, however that would likely change.
I would advise continuing to advocate for addressing this (to the extent it’s an issue) in the core app as you have been. You’ll get a better result for this issue, one way or another, at the end of that process.
Building a plugin won’t necessarily get you the “right” result faster (getting this right in the initial version would take a while) and you’ll end up with a worse result in the end for this kind of issue (i.e. a structural SEO issue).