I'm doing X forwarding for 15 years and unless you have ~20mbps symmetrical lines, you can't do anything productive.
However, if you absolutely must, use X2go.
However, if you absolutely must, use X2go.
When the updates are occasional, fine, but when you call make or run something which updates fast/creates a lot of output, things get hairy, quick. Even on local networks with a couple of connections. Been there, tried that, experienced it all.
X2Go transmits the image, compresses it, and can work with much slower and higher latency network connections. It can also resume sessions.