Absolutely, UDP is used for real-time video (Skype/Zoom conference calls etc) because it is light weight, and if packets are lost being real time you can't do a lot about it as the moment is gone. UDP packets also can and do arrive out of order and the network stack delivers them in that out of order state, the software/hardware upstream would need to implement it's own mechanism to identify and reorder the packets. TCP packets are just as prompt unless they go missing, and if they do or are out of order the network stack itself deals with this and the software upstream gets an error free stream and is unaware of any problems lower in the stack.
For a network tuner the only negatives with using TCP is the hardware requires a bit more memory and CPU power to deal with the error handling, but Silicondust introduced support for TCP on their tuners to stop errors seen with UDP that made it seem the tuners were not always that good, where in reality it was the persons own network causing issues. Plus another issue is UDP packets are larger than the transport stream packets, in the case of the HDHomeRun tuners the UDP packet size is 1316 bytes, so each UDP packet holds 7 transport stream packets, so a single UDP packet lost actually loses 7 transport packets so the error is magnified and it is harder for the decoders error handling to "ride" over the missing data.
Since using TCP I've recorded hundreds of hours and testing the resulting transport streams they have not a single packet error, this wasn't the case with using UDP, so it is definitely better and nice that the HDHomeRun tuners have a nice power processor to be able to offer TCP.