No, neither did I. Thanks for checking!
I think this (together with this) really is a design flaw/shortcoming in obsidian core. Not sure it makes sense to try and work around that via plugins. Unless I fail to grasp some design principle that requires the current way of handling aliases, I’d say that Obsidian’s implementation of aliases is incompmlete and I would almost assume that fixing this already is on some roadmap.
The challenge may well be that there are probably varied ways of using aliases at the same time as aliases are widely used so that changing the core behaviour to fix the above problem may break something in some other use case.
But so far, I have failed to imagine such a use case. Can you come up with a scenario in which the propsed solution might lead to problems?