Another possibility to merge instructions for managing static data in SSDT projects

I have a database in which some of the tables are relatively static. To keep the data synchronized between database versions, I use the merge statements generated by sp_generate_merge in the post-deployment scripts. That works well. This, however, disturbs my DBA because the merge instructions are problematic.

The merge statements are relatively safe in my use case, but if there is a way to generate a safer T-SQL for the same end goal as simple as sp_generate_merge, I would much rather do it. .