It does not look like anything capable of breaking your system. VST hosting, unlike rewire et al, is taken care of by the individual DAW. This is why all the NI stuff ships as both executable and vst dll. Unless your DAWs (max included) share a vst plugin folder, sadness should not occur.
Then it would break down by individual daw, based on vst loading. Each daw will have a separate whitelist/blacklist of vsts. Once a particular vst fails to load/breaks the daw it will refuse to load it until you force it to by either manually overriding in daw configuration or removing it from the vst folder, running the daw, and replacing it to make the daw auto-redetect it.
NOTE: I believe the identical functionality is availsble (for "free") in REAPER. Yay reaper!
That is to say, this thing in and of itself would get blacklisted – not the 32-bit vst. Most 32-bit vsts I have encountered run on 64-bit (waves is a sad exception, but they ain’t nuthin compared to voxengo anyway) without assistance, just in 32-bit "compatibility mode" (IE no performance boost from 64-bit system)
Sure they should be. In fact they should be loaded along with the bridge. If you use the bridge, then you will select the plugin you want to bridge. If you use the unbridged plugin it will run in 32bit mode no problem. You should even be able to run 2 instances of the plugin, briged and unbridged.