Comment 4 for bug 254576

Content import is a hairy problem, so much so that I would rather move it
out of the "setup profile" world altogether.

I tend to write export / import scripts which use the underlying GS machinery
(the export / import contexts, and the adapters), but which drive the process
outside the scope of the tool. In these cases, I often "scribble" on the context
to record information in one phase which I will need later (e.g., references which
need fixing up, etc.).

Perhaps we could "bless" this scribbling with an API, and
solve your use case by having the import adapters record the created content
paths via that API: you could then run the reindexing in bulk at the end of the
import, where you could control the batch size, etc.