Hi Alex,
you are welcome!
I am not sure it'd properly work. There are other files and folders that have to be in sync with those devconfig folders. What I still don't understand, why don't you just fire up your NWDS on the target client machine and simply import the corresponding development configs to your NWDS ?
NWDS is only a client, the party goes on the server. 
Without connecting to NWDI it all makes no sense even if you would find a brute force way copying devconfig folders from A to B. You could acually even delete your entire NWDS installation from the original client machine (considering you have no checked out activities) and still nothing would get lost because everything is on the server (the archives are in CBS and the sources in DTR). Once deleting your local NWDS workspace you could reimport the given development config in a minute and then you'd be there were you were before the deletion. But consequently you can do this on any other client machine, even if it is on the other side of the world (having proper connection to the server (NWDI)).
Cheers,
Ervin