Isn't this analogous to using open source software in a setting where bugs in the software might result in financial losses -- i.e. is there not a "NO WARRANTY, USE AT YOUR OWN RISK" clause that you can attach that is strong enough to shield you from any potential liability?

If you can get the legal angle sorted out, I'd personally find these sorts of documents useful. As for waiting for a version without "holes", that sounds like waiting until the software is perfect before shipping it :) It's not like a theoretically "bulletproof" set of templates would stop anyone from suing you anyway, if some company tanks and the investors are looking around desperately for someone to blame...