One immediate problem that I have found with running EMC and Tkemc on different computers is with the emc/programs directory. When opening a file, Tkemc displays the local file system and then tells EMC to open the file based on the client directory tree. Should the file not exist on the server, or the directory tree differs, then an error is generated. One fix for this is to mount one common NFS directory in the same place on both computers.
By default, the client tkemc uses emc.nml and emc.ini when starting up. If the client computer is also used for running EMC locally, you may want to consider having a copy of the programs in a seperate directory. With some experimentation with ini parameters, it sould be possible to have two configurations co-existing in the same directory.
One area of particular concern in this day and age of network security - The EMC server will accept connections from any client on port 5005. If you are running the EMC server on a large network or connected to the internet, then you must look very carefully at the security risks. To have a remote user connect and turn the spindle on whilst you have your fingers in the way should be incentive enough.