Yeah, it's a good idea!
I've uesd Nexpose, metasploit, nmap, packet captures, aircrack, and a bunch of other utilities (ala BT5). What gets me, is that sometimes the most obvious holes in security are ignored and it doesn't take big fancy tools to tell you that. Just a hex editor and some time...
I'm not an infosec professional by day, and wouldn't feel good about presenting as one. Part of me wonders why Pool owners and other businesses using bitcoins wouldn't simply hire a reputable security company for an assessment. 10-30k can get you some very good information to get started after interviews and the internal/external pen test.
Ultimately, I think best practices surrounding wallet files is needed for the community. The idea of recommending *nix as a way to secure the wallet seems inherently flawed. I say that because I'm not so sure the platform provides the security, but the security practies (e.g. not using a box where you send/receive coins from for any other purpose, and other practices).
Well, consider this: How many reputable security companies accept BTC for payment...? The idea is that we would be the first and we would be doing it for better prices.
Also, I wasn't recommending *nix systems as a way to secure the wallet, but more than 90% of users' boxes are going to be either Windows or *nix based systems which is why would be implementing security testing/fixing on those systems. And I'm sure that nearly 100% of mining pool servers WILL be *nix based as well.
I agree, the BEST way to keep your BTC safe is to keep them in offline storage media but your BTC HAVE to cross the internet to reach you in the first place which means you WILL at some point in time have to place a box with a wallet online to receive BTC (unless you're storing your BTC somewhere online which is a REALLY bad idea), I would like to help protect those people as well as pool owners.
If you're interested, let me know and I will send you some info and I guess "interview" you through messaging.