There are alternative solutions you can use on Windows Home, e.g. any of the VNC flavors (UltraVNC, TightVNC, RealVNC). All of those require you to install a server component on the machine that you want to remote-control, which you connect to using a viewer component on your other machine.
TeamViewer uses a similar approach, but it also provides some back-end services to authenticate and manage access to the machines you want to remote-control. TeamViewer is frequently used by software companies for remote support, allowing service agents to access your machine remotely.
What I dislike about Windows Remote Desktop (and why I don’t use it even though I have Win 10 Pro on my audio machines): when you remote-control a machine with it, the local screen is locked, only the remote screen shows the content. When you close the remote session, you have to re-login to your local machine. So you can’t see the desktop on both machines at the same time.
The alternative solutions like VNC all allow you to do this - they mirror your screen content to the remote-control machine, so I can work normally on my touch screen and at the same time have a remote session open on my PC for editing and any detailed fiddling.
All these solutions have one thing in common: they need to copy your screen content and send it to your remote machine via the network - this will cause CPU load and some latency, especially over Wifi. Since I don’t want to degrade my audio performance massively with my remote desktop solution, I have tested a number of solutions on my Live Cube now, and I’ve found that TeamViewer is so far the one with the lowest CPU impact and with a minimum of hassle. Plus, it’s free for personal use.