you can redirect all of you HTTP ports to MWG and since 7.5.1 also FTP. When redirecting non supported traffic such as SMTP, the result is likely not going to be what you expect (carefully said). MWG will only understand the protocols it supports on the proxies and thus will happily reply with a 'not supported' message to SMTP and other protocols.
Thank you for the reply, Michael. It's what I assumed, but my company is currently trying to curtail a huge bandwidth issue so I'm trying to find ways to restrict not only inherent web traffic (http & https) but also stuff like torrenting and other applications that may hog the bandwidth. Inside the web application itself, I've observed application lists that explicitly mention torrent variants (eg mininova, scrapetorrent, torrentportal, etc.) so I'm imagining that I'd be able to control torrenting with these lists. I'm also wondering if I couldn't use Application.Name to look for "uTorrent" then block all requests and replies associated with it. Is this making any sense?