Things went better today, since I wasn't trying to get any work done and had time to futz around with it. Some questions linger, however.
Last night I used Netview & Modem to send RTCM3 3.0 to TCP0 a 8010 on the T2 and saved the setting. This afternoon I set everything up -- TLS, T2, HPT435BT, and Jetpack -- and started off with UHF, which went fine once I got the TLS more than a dozen or so feet away from the UHF antenna (too close and it didn't work, must be too much RF). However, when I switched to TCP I got nothing. I scratched my head, turned things off, rebooted, tried starting up the devices in a different order, but still no TCP. Then I tried turning the TLS WiFi radio off before switching to the TCP profile, and turning it on after. That worked -- I found I could switch between UHF and TCP as long as I turned off the WiFi radio before changing profiles.
Then I remembered Phillip's comment that you had to end with UHF or port 8010 would close, so I tried ending with TCP and shutting everything down. When I fired everything back up again, I was still able to switch, as long as I turned the TLS WiFi radio off before launching the TCP profile. Happy with the result, I put it all away.
However: just now I hooked the T2 up to Netview & Modem so I could store the settings, and I see that TCPO a is showing no output protocol. I don't know if the TLS TCP profile will open that up again. I'll have to set everything up again tomorrow to see, but in any case I'd like to learn how to open that port while in the field. I tried nosing around Netbrowser on my phone, but didn't see any way to do that. If anyone can point me in the right direction, I'd be grateful.