Just to follow up: With "playing nice with the classes" I meant that Lucene could change the API in a way that we can't serialize (anymore) in the future.

Okay. I think you're right with sticking with the deleteByQuery(org.apache.lucene.Query) approach in the public API.
But I think the performance will be definitely slower than a real deleteByQuery(...) on the index.