To avoid unnecessary intermediate document materialization.

I don't know of any evidence that suggests this is a common pattern "in the wild," but it is similar to a case Xiaochen has mentioned where users have a replaceRoot followed by a projection that can be coalesced into a single DocumentSourceSingleDocumentTransformation.