Only things explicitly querying for information is "somewhat" sync, but then too the reply will arrive back with a sequence number, so the client API can just keep returning events and hold on to the replies until you ask for them.
X has many warts, but it being synchronous isn't one of them.
I seem to remember that there was a command line switch to run X (or some clients) in syncronous mode. It was mostly used for debugging.
Partly because the Xlib API is pathological in making it hard for you to minimize requests yourself. E.g. a lot of calls to modify graphics contexts can be batched up, but that requires Xlib to not worth requests immediately.
So hence there being some value on testing with different flush behaviour.
But this is Xlib specific, not really X.
Wasn't that just an issue with the Xlib interface? I thought Xcb made everything async.