This works well, when it works, but it seemed like at least with my setup it seriously exacerbated performance problems. Using the older OBS -> Zoom Windows solution of swapping out a video api DLL ("virtual camera") never caused performance problems but stopped working when Zoom started integrity checking/whitelisting all libraries[1]. I switched to the NDI solution which seems to be more "official" but gave up on using it as it would consistently work fine for a while, and then framerate would drop to <2 per second. This was on a reasonably new/high end machine (X1 Carbon 6th gen) with hardware video encoding in OBS so it almost seems less like an absolute performance problem and more like some kind of lock competition, but I didn't really dig into it very deep at all - it's possible that the NDI stack was doing some software encoding I wasn't aware of and that was just too much.
[1] this happened in the middle of all the zoom bombing and I've seen an allegation that Zoom did this to intentionally nerf that OBS -> Zoom pathway as it was found to have been used by many zoom bombers, but I have no idea if this is true so don't get out pitchforks about it.
[1] this happened in the middle of all the zoom bombing and I've seen an allegation that Zoom did this to intentionally nerf that OBS -> Zoom pathway as it was found to have been used by many zoom bombers, but I have no idea if this is true so don't get out pitchforks about it.