I have ran into the issue of exporting VS Code through distrobox, then having any VS Code / VS Code-insiders no longer able to open natively on the host (code 132 error).
Luckily, I keep system snapshots (through booting up into Rescuezilla) - otherwise, no matter what I tried, I could not get host-installed VS Code(s) working again.
This includes vscodium.
So to agree with @j0rge, I just stick to using host-installed VS Code.