Funny enough, I crawled through this exact code to comment on another thread[1] about telemetry in the console, but did so before the code was open-source.
The files you're linking to--specifically in terminal/parser--serve to tell a local developer running a text-mode application what VT sequences are in common use to help that developer figure out where to apply effort. We can also request that people enable these traces and explicitly view their contents, then choose to send us the data to help us troubleshoot VT parsing issues.
There trace logs aren't even wired up to the "telemetry" stream that everybody's so afraid of: TraceLogging is a local data capture solution first and foremost, and anybody can look at what's being produced using Windows Performance Analyzer. Nothing from this tracing provider leaves the user's computer.
I got a firewall popup when I opened Windows Terminal today. I forgot which IPs it was trying to communicate with, but it definitely tried to open some kind of connection.
Would you mind reporting this on our public tracker[1]? We absolutely do not expect there to be any outgoing connections unless you explicitly request them. Everything we're shipping is something visible in our public source, so you don't need to take my comment at face value.
You mind pointing out in the code where it "phones home to Microsoft to let them know what you've been doing with it"?