No, that is not possible. The Sysprep has prepared Windows and its state can only be changed on the reference machine by sysprepping the image again with an edited, changed Answer File.
Originally Posted by sratakhin
If you used Hyper-V vm as your reference machine as I did in the first video, and if you created a checkpoint as seen in that video at 23:58 when everything was done but Windows not yet sysprepped, you could simply apply / restore that checkpoint and remove the FolderLocations component from the Answer File, from the settings start tag (<settings pass="oobeSystem">) to next settings end tag (</settings>), everything shown in code box below:
<settings pass="oobeSystem"><component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
Removing that part would leave the Users folder to C: drive. Now run sysprep again and capture the new image.
On a production machine (the one you deployed the image to) this can be done only after Windows has been set up and the initial user signed in to desktop, at which point the Users folder already resides on the new location. To move it back to C: (or any other drive), see the part Upgrade, its Step 1 in this tutorial: Users Folder - Move Location in Windows 10 - Windows 10 Forums