I misread the post. My apologies. That will only partly solve he problem, and it's designed for new computers. It will sort of do so though.
The best thing to do is to ensure that a delta runs ASAP after the system is imaged, and it'll be placed only into new filters you have created. Anything "manually" assigned will remain of course. But as soon as a new system is deployed, and a Delta resource membership is run, all the old policies are "gone" and new ones appear.
The best thing to do is avoid manuall assignment to things and use filters.
You may however need to supply an example of what you've run into in the past. The simple truth is that most likely, even deleting a computer isn't going to resolve the issue, again, unless you've done manual assignment to filters in the past. Everything is dynamic, right? So if you assign a computer named X to HR, then HR policies apply, wether newly created, or in existence for 10 years. Deleting and recreating will drop it right back where it belongs.
So give us a bit of a better example of what you've run into in the past, and we'll discuss if this is possible or not, fair enough? You "should" be able to keep your asset history.