I can not agree with you. Read uncommited affects whole context while NOLOCK (equiv to RU) affects only given query.
Regarding data consistency - it's common chimera that NOLOCK=data integrity loss.
Please see eg. http://www.sqlservercentral.com/articles/Performance+Tuning/2764/
The core sentece is "There are no guarantees that your query will retrieve the most recent data.
Okay, this is application designer's choice. But there's nothing about data integrity, it's about recentness.
Do we need 0.0001sec old changes when editing order?
If yes, then do not apply NOLOCK, if no, then apply.
Again, designers choice.
Please consider NOLOCK implementation, it can have dramatical effect on performance, especially in multi-user scenarios.
Our ERP and B2B web uses NOLOCKs widely (hundreds of users), there're no data integrity problems in the ERP. If we didin't use NOLOCK we would go into gigantic lockings.