Hey @g-bougard,
Thanks for your detailed explanation and feedback. To add a further note to what was already explained, when we talk about supported and unsupported categories, we mean software classification under which the given snap can be assigned and thus granted or not granted classic confinement. The process is revisited frequently and snapd improvements are identified accordingly. This is needed to achieve the purpose of snaps being a portable and secure mechanism for distributing applications. And snaps achieve this through confinement, access declarations and this rigorous review process. Please see security policy and sandboxing for further information.
Remember that otherwise, classic confinement snaps run without restrictions and also run in the global mount namespace, which means great care must be taken for the snap to work reliably across distributions. When possible, we try to help publishers remain under strict confinement, and thus let them enjoy the benefits of a stable runtime environment.
Could you please let us know if you have included the suggestions given and if you could make your snap work as best as possible without requiring classic?