As I tried to explain, then all the torrent flows compete directly with your browsing flows, and fair queuing will on average give more bandwidth to the total of all torrent flows. That is the expected behavior.
There are possible solutions to this issue, from using bandwidth throttling in the torrent client over trying to use network namespaces to let the torrents run with a different IP address to using DSCP marking for the torrent traffic. So here is a question, what operating system are you using, and are your torrents mainly downloading or uploading?
For egress that is relatively easy, but for ingress traffic that is considerably harder, hard enough that solutions to that issue spawned long threas in this forum, like https://forum.openwrt.org/t/ultimate-sqm-settings-layer-cake-dscp-marks-new-script/53209/147.
Yes and no, cake can not really understand your intent or priorities, the best it can do is to honor DSCP markings in the packets to sort them into a handfull of different priority tiers, but yu are left with the challenge of applying these marks before cake actually handles the packets.
Becase all that cake sees are differet flows, and it tries to treat all of the equally, torrents win over brosing not because torrent flows get more bandwidth that browsing flows, but simply because you most likely will have a shipload of torrents compete against a few handful of browsing related flows.
Thinking this over, you could also try to limit the number of concurrent torrent flows to something sane, then cake should do the right thing out of the box.