Justify NOT using (nolock) hint in every query
You pick your battles and battles like this can't be easily won. We have a system where every DML is hinted with the ROWLOCK hint (irrespective of modifying one row or several thousand rows). I showed several examples why it really hurts performance but as the system is already working, there is resistance to change. Note that I convinced them enough NOT to use this going forward though.
NOLOCK has it place but I can recommend some good references showcasing the troubles of using it:

Microsoft SQL Server Development Customer Advisory Team blog – Previously committed rows might be missed if NOLOCK hint is used
Itzik Ben Gan at SQL Magazine – Clustered Index Scans Part III
Itkiz Ben Gan on sqlpass.org – Beware the NOLOCK hint