Hello vmproteau, thank you for mentioning my white paper.
One thing I noted during the testing of VMware ESX3.5 U2 VSS functionality, is that the domain controller did not start up in the recovery mode during the first boot. According to Microsoft documentation however, when performing a VSS-integrated domain controller restore, the system must be rebooted in Directory Services Restore mode when Active Directory is running on the server. To my understanding, booting in the DS restore mode is required so that the NTDS.DIT file is not locked with Active Directory services when the restore is performed. So I do not know whether or not ESX3.5 U2 VSS domain controller restore approach will be supported by Microsoft.
In contrast with this, our product (Veeam Backup) has the custom-tailored restore logic implemented for those Microsoft applications which require special restore steps to be made (Domain Controllers, Exchange servers). So in case of a domain controller, when restoring a DC backup you will actually see your DC booting in the Directory Services Restore mode first to perform the necessary restore steps while booted in this mode, then the DC would automatically reboot and start up normally.
I have published this follow up blog post with some videos of testing different backup and restore approaches for a DC running in virtual machine - essentially the same test that you are planning to perform. There, you can also find the video showing Veeam Backup DC restore process if you are interested.
Hope this helps!