Hi ckc8302-
Your assumption is correct- none of the single- or multi-slot USB, ethernet, or wireless CompactDAQ chassis are capable of running code in a stand-alone fashion like you are used to with your cRIO with LabVIEW RT and/or LabVIEW FPGA. You can use a stand-alone cDAQ for this purpose (like the cDAQ-9139), but that almost certainly defeats the cost-saving goal you're trying to satisfy for this case.
You are also correct in saying that USB cDAQ (9171, 9174, 9178) are supported with LabVIEW RT targets in general, but the caveat is that they are only supported with x86/x64 targets like cDAQ-9138/9139, cRIO-9081/9082, and PXI systems. The value cRIO controllers use a different processor and O/S architecture to implement LabVIEW RT support, and those targets are unfortunately not supported by NI-DAQmx and CompactDAQ.
One option you could consider would be to purchase an inexpensive computer and either run a version of Windows on it or make it into an RT desktop for use with LabVIEW RT. You could then use that to host your proposed USB cDAQ solution, and you could run LabVIEW code on that desktop machine to publish data over the network for consumption by your existing cRIO systems. The only other alternative I could think of at this time would be to continue cabling your TC sensors out to your cRIO systems like you mentioned.
Hopefully this helps-
Tom W
National Instruments