Customized vault not working (state_updating_resumes_at) [MC-268618]

Expected behavior

Customized vaults (with a custom loot table) from generated structures or placed jigsaws should be lootable (first time).

Observed/Actual behavior

When generating a structure or placing a jigsaw with a customized vaults players will be unable to loot them.
This seems to be related to the NBT server_data.state_updating_resumes_at as mentioned in the MC-268618 report.

Steps/models to reproduce

Create a structure with a vault that has a custom loot table.
Generate the structure or place it as a jigsaw in an existing world.
Attempt to loot the vault (for a first time)... this shouldn't work.

To fix the vault use the fill command to replace the vault with one that has server_data.state_updating_resumes_at set to 0.
After this looting the vault should work.

Plugin and Datapack List

Custom datapack with a structure that has vault with custom loot tables.
No plugins available.

Paper version

Any version since Trial Chambers (vaults) have been introduced.

Other

While this seems to be an issue for vanilla minecraft, having a solution for Paper servers would be very helpful.
See https://bugs.mojang.com/browse/MC-268618 for more details regarding the issue.

Reproduce the issue with a custom datapack structure containing a vault with a custom loot table, then repeat using a jigsaw placement. Compare the vault NBT, especially server_data.state_updating_resumes_at, with the fill-command workaround; done means first-time looting works for both generated and placed vaults without manual replacement.