I spent the weekend implementing an IPC based solution to this problem, and have a prototype NDI source working over shared memory under Linux now. I'm not a strong Windows coder, so it will take some time for me to get it ported, but I expect to be done with most of the work by the end of the week. I'll be publishing my code, both for the OBS plugin side of things, as well as the other side of the IPC link(the "ndibridge" as I call it). Between them there's a shared memory link I designed for moving A/V data between processes, not restricted to this particular case.
I'll let the decision on inclusion of the OBS side of the plugin into NDI be up to the OBS project, since at the end of the day you guys decide how to interpret the GPL in this case. The ndibridge program contains no OBS code, and thus doesn't have to be under the GPL. Likewise the OBS plugin contains no NDI SDK source, and thus is not covered by the NDI license. I will be publishing binaries(so users don't have to request access to the OBS SDK first) along with the source for this. As dodgepong says the IPC route can be considered a loop hole and is probably frowned upon.
I've also built an NDI output, that uses the same IPC link code, but since OBS Studio doesn't currently appear to support custom outputs I haven't had a chance to test it out yet. I might just have to create some functionality for custom outputs :-)
So NDI support will be there(and in fact is already here if you can compile an OBS module yourself), but it may require a separate download :-)