A lot of what X11 does is instead handled by Wayland "compositors", they deal with almost all such policy logic. This is largely the same situation as on Windows or macOS, which Linux desktops are finally starting to catch up to.
A window close event goes to the "compositor" of a surface, without being aware of which PID may have caused what is currently rendered on that surface.
Windows and macOS do the same, if only because they have a single "compositor"/window manager.
As a frequent user of xkill I was surprised by that too, but I remember reading somewhere that making a terminal application kill another application's window is not allowed by design. Reusing a sibling commenter's analogy, it's kind of like some javascript functions in the browser can only be triggered by user actions for security reasons.
The compositor, however, is allowed to kill the windows it's showing. So if you want to kill a window, you can ask the compositor to do it for you. Gnome, KDE [0], sway [1], etc.. each expose this functionality in a way that differ between each other.
[0] https://www.reddit.com/r/kde/comments/1242w2e/wkillsh_an_xki...
[1] https://www.reddit.com/r/linuxquestions/comments/ufw7tj/is_t...