"real" mouse goes to "console" instead "rdp-tcp" when using rdp

Question

Hello everyone. I have a stupid question. I want to connect a "real" mouse (for the so-called "relative mouse" mode) to rdp. But the problem is that remotefx does not work and I tried to connect via some "usb over ip" leads to the mouse going to "console" instead of "rdp-tcp" and is displayed only on the host machine's lock screen. I saw some videos on YouTube where people connected the mouse to rdp and their mouse works as it should there.. I did a study by installing windows10/11 in a virtual machine and immediately without making any settings I tried to connect the mouse through the mouse "emulator" via android and also via usb-over-ip but the result is the same - it gets to the "console". What's the problem? were those videos fake or am I doing something wrong? how to make the mouse get into "rdp-tcp" or at least make rdp run as "console"? (manuals about /console and /admin don't work, the option to write "PATH WIN32_TSPermissionsSetting.TerminalName="Console"" into the registry also apparently doesn't work on new windows, shadow connection is too slow) I'm at a dead end. haha.
(in general, I doubt that anyone will be able to help me, since this is clearly a very strange and specific... "problem")