You'll need to create a local user service account in your template. You can have your post-clone script delete that user.
You could bake the scripts into the template (so they run using RunOnce, or in linux, init scripts). You can also be sure that VMware tools are installed, and if so, use the VMware API GuestOperations manager to run a script in the GuestOS (GuestOps doesn't require network connectivity as it goes through the HostSystem). I've used this model to re-ip Windows and Linux guests in the past.
There is a QuickPrep that VMware View uses as well, I think it may avoid the SID regeneration to speed up the boot process after cloning. But basically you'd be doing your own custom address reconfiguration to avoid the sys prep process. On Linux, I don't think you have this problem as the customization process is just changing network configuration. Windows I think all the customizations are tied to sys prep (or at least if you want to change the domain it is).
You can test it quickly enough by just doing a customization spec with network and dns name configurations (skip the AD domain). You might not need all this complexity and can just use a minimal customization spec (I haven't tried it on windows like this in a while).