If you can avoid it though.. isn’t there an overhead in that transforming index always happens at startup, there is no check to see if the distributed cache index id is unchanged, so just let examine rehydrate the index from the persisted files?
Obv depending on the size of you site (content,media,member nodes) and which index you are transforming the hit on restart may be acceptable?
Also the original query is to match on the whole path, not on an id in the path? I think slightly different, as any node with id in it’s path would get the eqv of descendentsOrSelf, and not just descendents?
In fact re-examining that 
.. would a match on ParentId not be sufficient?
With the caveat you’d need to do a range query…