Firmware
In relation to the above explanation (and I admit I only did software programming to a very basic degree and never professionally), it seems very unlikely to me that you can interrogate the driver and can get back a result of "Geek Out HD Audio 1v5" or similar and yet you cannot do that for your dfu update program. Can you not simply write a wrapper that recycles the code that you already have for the control panel app and do a check before passing on the reference to the file to your dfu update program?
...
If I go to window's control panel, I can clearly see that under the LHLabs USB 2.0 devices tab, my geek out is identified as LH Labs Geek Out. How do you not know what device is being attached at the time?
...
Anyway, I hope Larry comes back on this because I don't think your answer was satisfactory given you do not have the full picture or technical competence on firmware writing.