I’m not 100% on the paths regarding the mounts and where the containing files are accessible, but it looks correct to at the moment. One way to test this is to check if the user you are using to run the Jellyfin container is able to access the files without additional input/steps.

If your user can access it, then Jellyfin will be able to do that as well as soon as you have mounted it in the container.

The drive will be mounted by the host and you can use that to also decrypt it. This way Jellyfin in the docker container doesn’t know that the media is stored on an encrypted hard drive.

Terms of Service; Didn’t read does that, but I don‘t know if it is the one that was shared previously.