It really doesn't matter what criteria he has to find duplicate rows. Making a copy of a table and then cleaning it up in not a good way to go. Just clean it up by deletes on the original.
You CAN do what you say, but it creates a bad programing habit. When you have a table over 1E6 rows and you make an image to it you could run out of resources. I'm not talking about RAM, I'm also speaking about disk space. Your site could stop accepting emails, logins or user uploads.
It is not a good practice, but I will not put a gun to either one's head.
Saludos
Gerardo