If I wanted to though, how would I do it?
It will not correctly track a trunked system; instead, it basically receives transmissions as if they were not trunked.
If you have a single conventional channel, where the database shows a specific color code, slot, and talkgroup, you can program that conventionally, with all those specific details, & it will receive it when active and the scanner is in that part of your scanlist. As long as you specified the talkgroup in your programming, you would not hear other TGIDs that might be on the same frequency. Note that if you specify, say Slot 1, then you would only hear that talkgroup when it is active on your specified frequency (and color code)
and it is using Slot 1. If it instead used Slot 2, you would miss the transmission.
For a trunked system, you can set it up
as a trunked system, with the sites & talkgroups entered. The scanner will then access that system, to see if any of the talkgroups you've entered, are active on one of the trunked systems frequencies, then the scanner will receive them. Again, it is
not actually trunk-tracking the system, just looking to see if any of the specified TGIDs are active on one of the frequencies programmed for the site.
You can program only the specific talkgroups of interest, so it will ignore those not programmed. But if it is a fairly new system, and you suspect that there be more users that what are in the database so far, you can enter a wildcard, which will then cause the scanner to stop & monitor
any active talkgroup on one of the site frequencies. Note that when programmed as a 'trunked' system, the scanner would stop on any active talkgroup that is programmed (if a wildcard is in use it would stop on any activity), regardless of which slot is used.
I've run across quite a few conventional DMR channels, especially for smaller towns, where the same talkgroup is used for both Fire & PD, but, say, Slot 1 is used for Fire, and Slot 2 for PD.