I guess my thinking is that should be part of the upgrade or update process - whenever antiXSS rules are changed, they are applied at that time. It's having this button there as if it's something you'd run for periodic maintenance that seems insane.
I'd definitely save input that breaks the rules when received, too - but maybe in a separate table.
However, the 'defender' in me can think of a situation where this would be good:
Input filtering mechanisms have improved to deal with new attacks/problems, but old data is not 'new input', so you'd apply the updated algorithms to existing data.