While you're going through the views, procedures, functions, etc. to find all the joins, do yourself a favor and take note of the data types of the columns involved in each predicate.  If it's as bad as you make it sound, then you'll likely have columns of different data types being joined together.  This implicit cast is devastating to performance, so you might as well make plans to fix the data types while you're identifying the joins. 

This sounds like it's going to be a pretty serious release script.  I've had to undertake efforts like this and they aren't trivial.  There are very few absolutes in SQL Server, but my experience is that what Gail said is absolutely true.