None of those are programming. They are communication and admin. Which are completely different.
Well, if it's not worth writing with some care then it's not worth writing at all. If it's worth writing with care, then your typing speed is not going to be the relevant bottleneck, unless we're talking about a hunt and peck typist.
I take it as given that anything one writes, whether code or English, should be read and edited three times before moving on. 80 wpm vs 50 wpm ain't gonna matter if you're doing this.
Here's what I've noticed about fast typists: They produce large volumes of hurried and poorly worded and edited crap. Yegge, my current boss, and one of my co-workers fit this mold. They type very fast, and I frequently have no idea what their writing is about, or am annoyed with the excess verbiage.
The best writing is re-writing. The best coding is refactoring. In both coding and writing the bottleneck is going through what you've written two or three times and making the necessary edits and stopping to think. First pass typing speed is absolutely not the bottleneck to producing anything of quality. If you want to churn out unreadable or unmaintainable crap, belting out functions at 90 wpm and then moving right on is a good way to go.
It's not a matter of habit, I just always find ways to better express myself when I take my time and correct those "problem spots," be they in code, email, or other correspondence. It's not that I doubt my skill as a writer, but rather, I owe it to my reader to be thoughtful and patient, just as I hope they will upon receipt.
The only thing I need to prevent is overuse of "etc." It's a tempting habit and lazy, imprecise, etc. When one uses "etc," they leave it to the reader to complete their thought, which is weak and clumsy.
Keyboards will continue to be the primary means for entering code and English text for quite a few more years. So it's rather silly to put off learning touch typing now while waiting for practical speech recognition or some kind of BMI to show up.