This is what a lot of downstream data processors and/or tile providers do in one way or the other to not have the vandalism in their systems or tiles. The misuse of the QA layer (OSMF minutely updated tiles as a mapper feedback tool) as a map tile provision elsewhere where this would not be needed is the mayor problem of giving a vandal actor the exposure he wants. But this has been discussed elsewhere here to no avail. It’s probably best to keep that question in mind but not to open it up here again. I think a lot of people in the OSM community just need some stress-level rest before the community of OSM goes into any strategic decisions (also in regard to the upcoming vector tiles).
The OWG (and others from the community that help them through pull requests or code improvements) is doing a tremendous job of lessening the impact of vandalism waves every time they occur through analysis and finding solutions post-incidient but this is a cat-and-mouse game. We can all be glad that e.g. the methods used in last year are not available anymore for those vandalism acts because of the improvements in APIv06 and in the rendering/updating toolchain used by the OWG.