I am not sure how to build the view you are looking for, but have you considered enabling PIRC on the Database.  PIRC is Purge Interval Replication Control, and it will stop old/outdated documents from replicating around your environment.

Look at this technote:

http://www-01.ibm.com/support/docview.wss?uid=swg21501675

You can export the people view into excel from both nabs and compare what is in this "corrupt: nab to see if they are in the prod nab.  You can do the same in lotus script if you have the ability to write some code

The other approach is to copy over a new rep copy of the nab to this server

LotusScript inherently looks at the last-modified value in the "added" section.

So while it'll take time to run, you can look for "date added", compare with date created, and figure out a cutoff date to show which docs probably came from the errant replication.

Also -- if it's only one server -- you could get a replica or OS-level copy from one of your other servers. One that you're sure has the proper set of docs.

Make backups of both "bad" & "good" Address Books.

Because we are a smallish company, the view that the developer did built me worked for me.

Because the docs that got copied back in had newer NotesIDs, they were at the bottom of the view.

I was able to locate the name of the last new user created and determine that all names following were the added "bad" names.

I assume that the view your developer provided was by Date Modified. If the Domino Directory is full-text indexed, you will see the option to search by date.  You can then change the criteria from date added to date modified.