Isn't that the point of the article? That you are offloading work onto the peopel you ostensibly want to get in touch with you?
(I'm not saying it's wrong for you to do so, just that your statement seems to line up perfectly with the author's premise that obfuscating your email address is taking your problem and making it their problem).
To me, that's conclusive proof that the form is worse than the obfuscated address.
Further, there's a balance to be achieved. I've analysed the types of people I want to contact me, and of those who can't work out my address there are two types. One type is those that I really don't care about - nuisance, spam, content-free, or time-wasters. The others that I do care about usually have a different route to me, one that's specifically tailored to them and made as easy as possible. That one has a specially designed anti-spam measure built into it.
Plaintext links have high usability. The mail is organized within the user's mail program where it can be retrieved, collated by subject, and so forth. It can be copied and pasted. It's the abslute best thing for them :-)
First, that depends. They may hit an existing domain with a catch-all mailbox configured, or they may hit a legitimate mailbox at your provider, where the receiver may or may not think to reply that they got the wrong address.
Second, what percentage of users (especially in the segment that might misspell their own email address) will know what to do with a bounce mail?
With an incorrectly spelled return address on a form there is no recovery mode at all, and they get no feedback that it hasn't worked.