There is a difference between what you can do and what you should do.
Let us start by explaining a bit about how scanning works, and the difference between scanning conventional channels and scanning trunked talkgroups.
A radio scanning conventional channels steps through each of the channels in the scan list sequentially. It first has to change the frequency of the local oscillator, then park on the new freq for a length of time to determine whether or not there is someone transmitting RF on the freq, then if there is RF on the freq, the radio has to listen a while longer to see if it is sending the PL or DPL tone for which the scanner is programmed. If yes to both questions, the radio then parks on that channel for as long as the freq and tone are valid, plus a "delay" timer. If the freq and tone disappear long enough for the "delay" timer to expire, the radio then resumes the process, going through each channel in the list and then starting over again at the top.
What this says is that, yes you can program a scan list in a PSR-500/-600 that has 1,000 conventional channels in it, but the time between sequential peeks at any given channel is so long that you're likely to miss a lot of traffic on that channel.
In a Motorola trunked system, on the other hand, the radio starts by listening to the data channel. It is looking at out-going commands to shift to a voice channel in response to a channel grant request by a user (this is known as an OSW, for "outbound service word"). If your radio sees an OSW for a talkgroup you have programmed in your scan list, it will switch to the freq of the voice channel declared in the OSW and wait for traffic. The radio will remain there until something happens, the something being either the issuance of a "disconnect tone" or the disappearance of valid freq and tone plus the expiration of a "delay" timer -- depending upon how the system and how the scanner are programmed.
What this means is that you could program a PSR-500/-600 with a scan list of 500 talkgroups. If the system is idle, the length of the scan list will not cause you to miss traffic on the first OSW pointing to one of your scan list members, but if there is any more than de minimis traffic on the system, you will miss stuff.
Now let's consider the case where a scan list mixes both conventional channels and trunked talkgroups. The radio will sequentially sample the conventional channels, and then it will change to the control channel of the trunked system waiting for an OSW that matches the scan list. It will stay on the trunked control channel until a "no traffic" timer expires, and that timer is reset every time the radio sees a valid OSW. While the radio is listening to the trunked system control channel, it cannot hear or scan any of the conventional channels in the list.
The foregoing does not address how a "priority" function works, but my fingers are getting tired.
There are two unwritten "rules" that are widely followed by system designers and technicians in the public safety world. Rules #1: keep scan lists short. Rule #2: do not mix trunked talkgroups and conventional channels in the same scan list. Hopefully, you will begin to see the rational for these "rules."