I think that would be dangerous to handle this at the X layer.

If we enforce a blind and strict rule about ambiguous getters, then we will get complains about applications no longer working.
The workaround we can offer them is to mark the non true getter property as @Transient: at least that's a way out.

But this means that the XLayer would have to understand JPA's rules which in the design decision we purposely avoided as the XLayer is used beyond just ORM. I proposed an alternative in HHH-10242.