Enchantment Rebalancing (Progression & Villagers)

The recent change of enchantments to a data-driven system in snapshot 24w18a has been an amazing addition to the flexibility that data packs provide. These changes and fixes have brought to mind the experimental changes with villager trade rebalancing. I think while it does provide another reason for the player to explore, I think most players will be against this change due to the significant slow down it would bring to the middle stage of the game. Currently, there is a feature where items with certain enchantments cannot mix enchantments with another. (Think Infinity and Mending on the bow.) I'm proposing a new optional enchantment field: requirements. 

"requirements": {
"enchantment": { "type" : "namespace:example", "level" : 1
}
}

Requirements is an optional field for enchantments, which takes a given enchantment as well as the level of said enchantment. This would mean that the only way the given enchantment could be applied to a non-book item, is if the non-book item had the required enchantment at the specified level. This would allow for careful design of enchanted gear, where you have to take certain enchantments to unlock ones later on. This would also be a great way to push player to interact with curses more often! You could introduce a few new curses, and make them requirements for treasure enchantments like Mending or Swift Sneak. This would also make randomly generated gear more valuable, because it could have treasure enchants without the curses applied.