While we have made no progress on a flashable zip file method of doing the NV edit, I have tested and confirmed with P3 Droid and myself that this edit can be performed using RadioComm with Factory boot mode selected from the boot menu.
The primary advantage of using RadioComm instead of DFS or other Qualcomm based NV access tool is that the drivers do not require forced loading on Win7 64 because the QC device interfaces are not loaded in Factory mode and the normal Motorola USB Networking driver is all that is needed to access the device and perform the edit. RadioComm also has a better UI for NV reading and writing and the port selection is not required. It is a very intimidating piece of software in it's own right and any of these programs are very dangerous to use given that you can easily break your phone with any of them if you write the wrong things to the NVM.
I have been using RadioComm for years and am the one largely responsible for it's use for various purposes becoming popular on the web, so I am very comfortable with it and it is the premier tool used by Motorola engineers for their needs.
I will writeup the RadioComm method after I have gotten some more confirmation from other testers that it works for them.
I have confirmed it's working for me under Win7 64 and WinXP 32.
Edit: Better yet, I have made it into an NVM table file that RadioComm NV/SEEM feature can write in a single preconfigured operation that many users may find easier than manually editing the NV items.
This is good news for other reasons as well. I had been having a hard time using this feature in RadioComm because the latest version available does not directly support the MSM8960 chipset and I could not effectively run the large table files we have for dumping the full NVM. I am running a full dump now and it has completed approx. 20% of the read operations in about 15 minutes.
This is opposed to about that many after reading for hours with other methods. RadioComm also has access to some items that cant be read with QC software because it suspends the device before reading the table. This mode is not supported by QC test commands.
Very excited now!