I doubt ssh or simple sh is a matter in this case. You can do simple sh:

qvm-run --pass-io {VM_name} -- ls

Security model is not to do anything non-admin related from dom0: if you "own" dom0 you can do everything.

Allocating amount of CPU cores is a feature of VM. Not sure about dynamic though. There is dynamic flag about memory, not CPU. In practice it looks like CPU is shared among all VMs, no need of special flag for it.

I use Qubes because of one exact feature: single Desktop Environment for windows from different Virtual Machines. And AFAIK there are no alternatives.

Use it for work, development, personal tasks for about 2 years so far.

But it has many restrictions, e.g. gaming is problematic because of this single "main" desktop and trucking cursors bug, recording screen when there are several monitors is bugging and problematic, streaming or working with graphics is problematic, development that requires other virtualization like android (as i heard) is problematic (though docker works, tested).

This OS is enough for my tasks, I like concept of separating activities, e.g. when i share desktop on skype, people see only skype's VMs windows. And single Desktop Env is killer feature.

But because of many restrictions this OS is definitely not for everyone.

For gaming I would just use a different machine. Trying to use an OS like this for that is always a compromise.

Also remote desktop cannot be done at least by usual means. And this is big No if you need to work remotely sometimes.

xfreerdp works just fine, however it requires some fiddling if you want to use it on multiple monitors.

Is rdp server in dom0 or in VM? Connecting remotely to VM at most i was able to see opened VM's windows, but no keyboard/mouse interaction because dom0 is responsible for it.