What feature do you want to see added?

On bedrock unsafe enchantments don't appear to display roman numerals above the max level.

For instance, Silk Touch II only displays as "Silk Touch," on bedrock. The server function still works obviously, but I want bedrock players to be able to differentiate between the two.

I know I can probably solve this by raising the max level of Silk Touch through datapacks, since my custom enchantments all work fine. So it seems Geyser properly takes care of that. However, there are some instances where we want enchantments to be unsafe, in my case I want the Silk Touch 1 to appear without the roman numeral, but if we raise the max level to 2 that doesn't happen, hence the need to make Silk Touch 2 an unsafe enchantment. Not to mention unsafe enchantments show up a lot in spigot/bukkit plugins, so make it display properly (if possible) would be really nice.

With unsafe (What we want):
"Silk Touch" Works on Java
"Silk Touch II" Works on Java
But bedrock shows "Silk Touch" for both

I'm not too familiar with Geyser's code and what's possible with bedrock; I mainly do spigot plugins. But perhaps the integrated pack could raise the max level of all enchantments to 255 (or 10 or whatever the max roman numerals display is) so that they display properly and then the java server would be authoritative on the actual level of each enchantment? Forgive me if that's not how it works, but just want to suggest it just in case.

Are there any alternatives?

Perhaps using custom mappings v2 you can match the item component of a given unsafe enchantment level and apply lore to the item? Edited: this doesn't appear to work since the bedrock_identifier has to point to a custom item, making it hard to change vanilla components.

Refrain from using unsafe enchantments or modify max levels through datapacks.