For torrents its a bit more nuanced, as it will depend on where the peers are...
If the peers are local there shouldn't actually be any throttling, if the peers are foreign it may be intentionally throttled or it may just be slower due to distance, especially if they are in europe or the americas.
For torrent clients which encrypt traffic between peers and to the tracker, network based traffic management shouldn't be able to identify the traffic as torrents.
Consider however that Simba uses CGNAT which means you will not be able to receive inbound connections over IPv4. If other peers are also behind restrictive NAT which prevents inbound connections then you cannot peer with them. You will be able to peer over IPv6 with any peers that support it. This also means that you won't be peering with other Simba customers unless you're both using IPv6. Peering with local users on the same ISP is usually the fastest and won't usually be subject to any traffic management measures at all as the traffic remains internal to the ISP (ie they don't have to pay any transit fees).
Depending on what torrents you are downloading, being stuck behind CGNAT could severely reduce your speeds as a lot of other users will be stuck behind CGNAT and may not have IPv6, or even without CGNAT have not configured port forwarding for single level NAT.