I love it, but it's a bit of an enthusiast's tool yet.
I've got a small-ish (4*7m) studio set up with a 98" TV, two monitors, a teleprompter and three Canon CR-N500 PTZ cameras and a separate control room in a side room. Everything's run on NDI. (Or NDI|HX in the case of the cameras) That's a very manageable setup with SDI, too -- until you start doing custom stuff. Let's say someone brings a laptop and they want to show something. That's an HDMI to SDI encoder (or a long-ish HDMI run) through the wall and into the capture card. For NDI, just install NDI Webcam Input on the laptop and run an ethernet cable to the wall port. Or, a HDMI to NDI converter that connects with PoE+ to the ethernet port along the wall. Either option, NDI or SDI; is quite convenient to put together on the spot, and safe for any laptop, company owned or not.
But let's say I wanted to put that screen capture up on the TV behind them, for the audience -- and on the teleprompter in front of them, as well as into VMIX. Ordinarily that would be a three-way SDI split from the source or an output from VMIX split into two destinations. Not hard to set up, but you'll have to have it lying around if it's a one-off, and you might need a commercial break to switch back to whatever you usually have on those monitors. With NDI, the TV and teleprompter are already set up for it with their own NDI decoders. Just match both decoders to the same encoder and you're good to go. Once the segment is done, just switch your TV and teleprompter's NDI decoders back to whatever you prefer. Powerpoint? No problem, just make the input an NDI source. A Teams call? No problem, Teams has integrated NDI quite well. Your PGM output, or VMIX remote call? Not a problem, all built in.
However. You are gradually introducing network complexity. If you don't have the proper backend, or if you're routing your camera(s) through the same network or running too many NDI output sources from VMIX, you ARE introducing risks of packet loss and stuttering as well as taxing your CPU. At worst, if you run your internet on the same line and network interface, you might even risk disturbing your live PGM output to your stream. That's obviously very bad, and it might not be apparent what's causing it, or you might cause problems only intermittently. (If for instance some background process on your PC kicks your CPU use up north for a few seconds)
Bottom line, if it solves problems for you, it's great -- if you are the network guy, or you have him on speed dial. If you don't, it's a bit of a risk and you have to be very precise and have good hygiene. Try to get a separate network set up for your NDI sources and get a good, PCI-E network card for your computer with two distinct interfaces for your NDI network and your Internet network.