I wondered if you can have a user-defined data type in tables which is always an identity column with the settings that you want. Then you would make developers use that data type in tables. I looked at this document but I don't understand what is possible, sorry.
After tables are created, you can examine the identity column information of one table at a time by using the "DBCC CHECKIDENT" operation.
For this I'd write a script that generates the "DBCC" command as text output for each table that has an identity column. Something like:
SELECT N'DBCC CHECKDB([' + TABLE_NAME + '], NORESEED)'
Then you need something to look at the result and find unsatisfactory values.
You can vary the command, to override and set the value used in the identity column in new rows, but you aren't prevented from setting it to a value that already exists in a row in the table, i.e. producing a duplicate key. That can be avoided by only making that change when the table has no rows. Fixing data that was already input without respecting your condition may need to be a separate exercise, anyway.