The SQL specification defines four transaction isolation levels, although a fifth transaction isolation levels appears in APIs including Java’s JDBC. That one is used to identify databases that don’t ...

That is not the case. What the NOLOCK hint does is enforce SQL Server's Read Uncommitted isolation level, which allows for what is known as dirty reads. What does this mean for your application?