Hmm, that's quite a log. Some comments:

import org.hibernate.search.backend.impl.batch.DefaultBatchBackend;

Not quite sure what the intention is here. DefaultBatchBackend as well as the interface BatchBackend itself are impl classes. If any of this is needed externally we need to move at least the interface into an spi.

import org.hibernate.search.backend.impl.WorkVisitor;

That's imo internal. Not sure why that would be needed by Infinispan query.

import org.hibernate.search.bridge.builtin.impl.NullEncodingTwoWayFieldBridge;
import org.hibernate.search.bridge.builtin.impl.TwoWayString2FieldBridgeAdaptor;
import org.hibernate.search.bridge.util.impl.ContextualExceptionBridgeHelper;

All these bridges can be replaced with custom bridges with Infinispan Query. I don't think there is a need to expose anything here.

import org.hibernate.search.engine.impl.LuceneOptionsImpl;

Not sure why the impl is referenced. Anything needed which is not in LuceneOptions?

import org.hibernate.search.engine.metadata.impl.DocumentFieldMetadata;

There is a public metadata API. Would this suffice?

import org.hibernate.search.impl.SearchMappingBuilder;
import org.hibernate.search.impl.SimpleInitializer

I guess you could do the same things w/o depending on this class

import org.hibernate.search.indexes.impl.DirectoryBasedIndexManager;
import org.hibernate.search.infinispan.impl.InfinispanDirectoryProvider;

Not sure why there is a direct dependency. What are the details?

import org.hibernate.search.util.logging.impl.Log;
import org.hibernate.search.util.logging.impl.LoggerFactory;

/
That seems just wrong. Infinispan query should not use/reference the Search logger. I would assume it has it's own logger as well?