We have a similar problem, but unfortunately some peculiarity in how Solaris quotas work prevents them from being useful for work space overruns. Or any kind of space policing, unfortunately. So a few times the whole system has stopped working correctly because a rogue program has used up all of our terabytes of work space.
Redirecting WORK= or USER= (or both) to the user's home drive should be possible. WORK= has to go into the configuration file, but USER= can go into either the configuration file or a program (or the autoexec).
Also, read up on UTILLOC, which is also used for some kinds of work files. Depending on your setup, you might need to redirect that as well.
We have dedicated work drives that are faster than regular user drives, so for us redirecting WORK would cause a performance hit. On Windows, we redirect WORK to a network drive so no protected health information is stored locally. Slower, but we don't want users to run big jobs on Windows anyway,