The question is about chroots, Waydroid or Anbox doesn't use chroot but LXC specifically which are somewhat similar but not really the exact same as chroot.
I have tried this myself. It doesn't work at all on a regular GNU/Linux distro due to some differences in the kernel. After swapping the kernel to a custom one built with Android-x86 Linux kernel patches integrated, the Android-x86 init executable runs at least (with the proper bind mounts to the chroot) but the system seems to crash or hang flooding the console/TTY with errors. host was also affected, some programs on the host started to hang after android init executable runs in the chroot.
Although I couldn't get the Android GUI, I got access to the Android-x86 console, ran adbd in the chroot and was able to connect from the host. It was a very interesting experiment for sure. Just like in Android-x86, if I exit the console with Ctrl+D it re-appears after a while.
I didn't go more further but thought that when the host is using udev+systemd and when you try to start the android init system in a chroot, they conflict together. Could be since the devices nodes and kernel are shared (/dev, /proc, /sys) without restrictions. Waydroid and Anbox use lxc which creates different namespaces for that.
On a side note, I would like to mention that not only "the console part without Xorg" is possible on Android-x86. I have also run a Xorg server on KMS/DRM directly from chroot on Android-x86 using startx/xinit. In that case Xorg is running in a separate TTY with hardware GPU acceleration.