Privileged container for fuse mount

Is your feature request related to a problem? Please describe.
Our container needs --privileged (or --cap-add SYS_ADMIN + --device /dev/fuse) to support CVMFS FUSE mounts inside the container. CVMFS is used to stream neuroscience software modules into the container at /cvmfs/example.

Describe the solution you'd like
Support for --privileged flag in wslc run, or more granularly, support for --cap-add and --device flags to allow adding specific Linux capabilities (SYS_ADMIN) and device access (/dev/fuse) to containers.

Describe alternatives you've considered
Mounting CVMFS on the WSL host and bind-mounting /cvmfs into the container via -v /cvmfs:/cvmfs:ro, means users to manually install and configure CVMFS in their WSL distro, not great for an app targeting non-technical users.

Additional context
Project: Neurodesk App, desktop app for neuroscience computing. CVMFS streaming works on Docker and Podman with --privileged, but is blocked on WSL due to missing flag support.

Appreciate advice for workaround if this feature won't be considered for future release.
Thank you!

Start at the wslc run entry point and inspect how container options are parsed and passed to the runtime. Compare the requested --privileged, --cap-add SYS_ADMIN, and --device /dev/fuse behavior with Docker or Podman, then validate that a CVMFS FUSE mount works inside the container.