Could cargo-miri's use case be covered by a crate? If so a shadow-env crate could be published and the migration guide could point people at the new APIs for the common cases and to the crate for cases more like cargo-miri.
I think having the shadow environment be opt in via a separate dependency would alleviate at least some of the concerns here about the shadow environment being the default.
