For the builder looking to circumvent this limitation, I just attached a .mcstructure file. It contains the original vault data inside. So, If you create a behavior pack, then put this mcstructure on "structures" folder, you can use /structure load ominous_vault ~ ~ ~ to spawn a functional ominous vault, or use a structure block and load "ominous_vault"
For the builder looking to circumvent this limitation, I just attached a .mcstructure file. It contains the original vault data inside. So, If you create a behavior pack, then put this mcstructure on "structures" folder, you can use /structure load ominous_vault ~ ~ ~ to spawn a functional ominous vault, or use a structure block and load "ominous_vault"