Dave -
In the end, to have your compromise, you have to make one.
Point 1: Problematic Roaming profiles -
Create 4 standard domain user accounts. Do not set them up for roaming - accept the default local profile setting that W2K offers. It will save the profiles locally on the W2K workstation but authenticate as you wish from the Domain (giving them the access to whatever you need to from the domain).
Point 2: Application Data - If saved anywhere local would be inaccessible to them when they logged back into the normal NT4 workstation (An unstated issue but a consideration)
If necessary, to overcome the issue of where they save their files, create a shared directory on the domain file server - They can create subdirectories there and give permission to the subdirectory folder only to their current and usual user account (so no-one else but them could get in there). Then when they log back into their normal workstation they could see the files and move them to their regular data folder.
This is the only real way I can see to make it a bit easier on you.
a. The "fluctuating" users can log in using one of the 4 shared accounts
b. They can move their data to a safe location easily.
c. You only have to add a limited number of accounts. Your only maintenance, if you need the security and trackability, is to change the password between different folks using the accounts. And that ony needs to be a quick "user must change password at next login" situation.
Even if this isn't answer you really needed there should be a couple ideas to build from.
Hank