Would be faster to boot up than @wordpress/env.

If it supports all our needs (install additional languages, WP-CLI access, no timeouts, etc.), then it could be an interesting option.

Our existing configuration steps would then need to be moved to a blueprint I suppose.

We could then also support loading (merging?) a plugin's custom blueprint for more elaborate runtime checks.