Chrome has separate code for dealing with each compositor. The bug would be in the code that deals with Wayland specifically.

If every other application / process is running fine, but not Chrome, then how is it a Wayland 'bug'?

Chrome doesn’t even run on wayland, unless compiled specifically on a new enough branch so OP talks about the version running inside XWayland. It can possibly be a bug in the specific compositor’s xwayland implementation or even in chrome. Also, your special ability to try out every compositors must be really useful.