Enums are always sequential in the register value
Even if a enum type is defined to be non-sequential in Python, they are optimised to occupy the least amount of bits in the register i.e. sequential. This is a complication if you want a consistent value of the enum when different softwares (e.g. ground software vs spacecraft software) read the register.
@jason.watson and @nico.desimone discussed this issue and decided it was not urgent to change. But this issue will document the discussion in case we return to it.