Yes, window management systems that are as old as X have that escape hatch of allowing positioning by global coordinates. It's pretty much impossible to take that ability away from applications when it inevitably becomes an issue.
"You don't want that - I know you don't"
You can try to frame this as pandering, condescending, mean or the devs having a personal vendetta against your workflow all you want, there are tradeoffs with such fundamental design decisions which have been deliberated over a lot. You either make global window position the sole responsibility of the compositor or you expose control to applications and get an unmanageable mess, which you can't fix.
Afaik, there are plans to implement additional client hints which applications can use to indicate desired window positioning or even manage relative position of multiple windows, but they don't involve direct access to the global coordinates. This is mainly a concern for complex multi-window legacy applications which are currently stuck on xwayland. See this for example: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/264
Do you have an issue that actually requires this or do you just have an issue with how a certain compositor handles window placement?