It turned out it was NOT a problem with NoMachine, but rather with the desktop session itself, with frequent bursts of CPU usage related to a /usr/bin/gnome-shell when the desktop was accessed locally. Since I was not interested in using specifically the Gnome environment, I resorted to the Mate environment: both the desktop and the remote desktop via NoMachine now work with no overload.
Thanks anyway for your prompts!
Andrea