An update on WiFi using Windows Remote Desktop between two computers (one scope side, one indoors) and terminating with a 4K UHD monitor. As per my previous post, cat6 cable works fine, but WiFi is more challenging. But I think I have solved it....
In addition to selecting <WAN 10 Mbps> as earlier suggested, try separating your dual band channels into separate 5 Ghz and 2.4 Ghz channels. This is easy with a BT Home Hub 5/6. You will then see an additional channel dedicated to 5 Ghz. Hence force your 5 Ghz wireless adapters to connect to that to improve performance.
If you don't have 5 Ghz wireless adapters, buy a USB plug in model and disable your computers internal 2.4 Ghz version via Device Manager. Note there are two versions, 433 Mbps and 870 Mbps. I found either work fine provided your network range is adequate. Mine wasn't, so I purchased a Netgear EX8000 wireless extender. Much better than my previous cheap dual band model and it also offers 'mesh' technology (much superior). The key to success with 4K 'end to end' does seem to be a need to ensure you are connected to the 5 Ghz channel. Simple 'dual-band' may mean you are auto-connecting at merely 2.4 Ghz.
However , tests using Windows ResMon utility suggest that bandwidth and network speed isn't the actual problem. Reliability of connection (distance/range) is much more important. What most surprised me was the load on computer and graphics card on the scope side computer. I am using two Intel i5 NUCs with Iris Plus 640 Graphics and Optane memory. I suspect you won't get a 4K display to run comfortably on much less (so I suggest you don't attempt with cheaper Compute Sticks.
Lastly, I question whether chasing 4K UHD is actually worth it unless using Hyperstar which increases FOV x 5, but correspondingly reduces magnification. The extra <zoom> is beneficial. However, at regular magnification (say with f6.3 reducer) , you won't notice much difference at 1080p, which is much less challenging over wireless.