I strongly agree that routine maintenance issues should not involve a number of things that many equipment suppliers and software publishers suggest.
Your point on drivers is confirmed in my own experience of maintaining hundreds of client's machines over years of time. This is especially true if you are maintaining systems running a vertical market application in a narrow environment.
I can't tell you how many times I've had to reinstall an older driver that insured compatibility just because another user/tech/whomever thought that a newer date is always better. As IT well knows, many (most?) driver updates are related to resolving a narrow need or sometimes quite minor incompatibility.
I think the original article, while well intentioned, just simply confuses installation (or perhaps, reinstallation) issues with routine maintenance issues.
I do believe in cleaning KBs and mice (mouses? meece? meeces?); a shot of compressed air every couple of months can sure reveal a lot of garbage that falls between the keys (actually, quite an amazing lot of garbage). This is especially true if you have a particular KB you like or depend on a particular KB (or one with vertical market or proprietary keycaps, etc.) for ancillary functions.
One disagreement: In all the years of owning my company and doing vertical market installation and maintenance, NEVER--not a single time--did a client ever ask why maintenance was taking so much time. Matter of fact, they were usually fussing at their employees about NOT doing even the small things that prevent major problems down the road. One of our upsell techniques was to point out how little maintenance is done in-house and what that ultimately costs in equipment replacement costs. We ~always~ sold 10-15% more KB/mouse/etc. than necessary, so that routine maintenance and/or replacement did not also involve downtime.
Otherwise...your reply was right on target!