I see the point and know the aurguments well, I've managed the deployment of 10,000s of Windows Machines. VBA Remediation isn't really that difficult any longer, putting that functionality into SharePoint, MUI Applications or even Web or WPF Applications typically offer better integration, stability, security and a much higher long term ROI.I have no doubt that VBA/ActiveX has been the conduit for numerous incursions, but what is the Risk/Benefit ratio. If we just consider the little Timmy or Grandma consumer then the R/B is fairly high. Likely, that type of consumer would not even know how to get to the VBAIDE.
A member of a mobile workforce, however, is probably in a better position to take advantage of the benefits that custom automation has to offer. Chances are the VBA routines are legacy/integrated/critical/mature, possibly expensive to rewrite: keeping all that at the cost of a little IT angst may be a great bargain.
I think the food/food poising analogy is apt. Just make sure there is some Pepto on hand.
If I run into a customer that can't or won't remediate legacy VBA based Applications, I would recommend a VDI Scenario and still look at RT for many of the mobile workforce managed via MDM (using Intune and System Center). Surface Pro 3 for roles that require the backwards compatibility or have business reason for x86.
I'm currently working with the ISV community on the Windows Server 2003 EOL and running into all the old bugs and security holes from that era, as we try to modernize their apps for Server 2012 R2 or even Azure.