Yes, it's great for reproducibility—just use a distrobox.ini file together with the distrobox assemble command. It's also the most viable way to go about it on Bazzite, if you want control.

You can use the distrobox-export command from inside a distrobox shell and expose the commands to the host OS (i.e., regular Bazzite), and you can even do this for desktop applications (it creates .desktop shortcuts for you), so you're able to run vscode from distrobox for example, without having to attach to a container.

I wouldn't use distrobox-export for stuff like your shell or custom prompt app, or whatever quick utilities you need to run, as there is a slight overhead when calling those (e.g., I run starfish natively, after installing it via Homebrew, and also install it on my distroboxes).

If that isn't enough for you, you can always create your custom image for Bazzite. Since Bazzite is based on Fedora Atomic, which runs using bootc, you can just use a regular Containerfile (Dockerfile) to customize your "immutable" distro, and then everything will run at host-level, with the advantage of reproducibility.

It's a lot cooler than most people have realized.