With a typical bug code works not as author intended it to work. Numbers of such bugs can be reduced by testing and better tooling. But software development as an industry creates incentive to be overconfident and not to question own assumptions: developers who don't stop to read documentation/standards/gather information in anther way deliver more features in less time.
So if they're going through the motions they were told to, but don't fully understand why (and don't QA properly) this is what you end up with.
Could also be a system using the same logic of surfacing every <a> tag link for tagging before deployment (based on the utm names, there's at least some type of semantic logic to the naming that indicates a person was involved at some level and knew it was a phone number they were tagging).
[1] https://docs.google.com/spreadsheets/d/1xDl9GdpuWB9kzXzWxKj3...
Most WYSIWYG email builders built into these tools are pretty painful to begin with, and especially so when content with links is copied from one tool to another. (Think of the poor marketing person being given various blurbs in Word, Gmail, etc. and told to make a functional email out of them while having to use a shitty WYSIWYG.)
Beyond that, most marketers I know have absolutely zero input into what email platform they use. Many organizations are stuck using antiquated, broken tools (I'm looking squarely at you, Eloqua) because of complex existing integrations they have set up.
I don't see this changing any time soon. Few marketing orgs have the IT budget and/or on-staff knowhow to fix this problem. Nor are they likely to be aware of it. Nor, for that matter, are they likely to prioritize it over the many more pressing things they could be fixing that more directly affect revenue.