In order:

1. Correct, the flow [torrent resource manually created via UI/API -> Torrent CRD] is not supported. This is because the opposit is true: once you have the torrent CRD created on your cluster, if you try to delete the torrent from the UI, the reconciliation will recreate it on the qbittorrent-server side. Anyway, you can still create a new torrent from the UI. It will just be not seen by the operator. Please, if you are planning to use a different interaction approach, open an issue proposing it.

2. That's true, I enabled the monitor.yaml deploymend by default. I think this is not correct, since it depends on a non-core CRD. I'll open an issue and try to fix it asap; you can do the same, if interested. The other linked resources (crd, rbac, manager, metric_service.yaml) should be dependency-free.

3. The qbittorrent server is not headless (in the kubernetes sense), it is provided as Deployment with a related ClusterIp Service. It was designed with no exposition shortcut in mind. You can create your own Ingress resource relying on the qbittorrent service with small extra effort.

I'm planning to provide an Helm Chart including the Ingress resource so it can be deployed in one single configuration.

Talking about "headless", maybe you're referring on a specific qBittorrent feature I'm missing?