I hate to rain on the thread here, but after review my suspicion is the scanner is performing properly. In ID Search Mode, it's searching for a sampling of talk groups from all 4 frequencies where in Conventional Scan mode, the scanner is only looking for activity on the frequencies and once it doesn't hear anything, it moves on.
That's not how ID Search works, and has nothing to do with the slow scan speed problem.
When the scanner is checking a frequency, the first thing it does is attempts to detect a carrier. If it detects a carrier, it will spend a certain amount of time attempting to demodulate/decode the carrier to see if there is any intelligible traffic on the carrier. If there is digital traffic on the carrier, the scanner will look for a talkgroup ID. When it finds one, it compares the talkgroup ID to IDs in the database. If it finds a match, it will check to see if the Service Type of the matching talkgroup is enabled. If so, the scanner will play the traffic.
If no match for the talkgroup ID is found, and the scanner is in ID Scan mode, it will continue scanning on the assumption that you only want to listen to known talkgroups that match selected Service Types. But if it is in ID Search mode, it will display the talkgroup ID and play the traffic regardless of any other consideration, on the grounds that you want to hear new talkgroups so they can be categorized and added to the database.
The hang problem is happening before the scanner gets to the ID Search/Scan part of the process, either when it is attempting to detect a carrier, or trying to demodulate/decode the carrier to extract the DMR digital data. My guess is that the scanner is erroneously assuming that DMR One Frequency site freqs are always active (like trunked system control channels) and is wasting time trying to decode DMR data from a non-existent carrier.
I did notice you don't have an FL assigned either, where I do.
Wrong, the two test systems were created in a favorite list. They do not exist in the main database.
If UPMan can add anything here, it would probably help. From the video and description given, I can't see a firmware or scanner issue.
It's a definite problem. There shouldn't be any noticeable difference in the speed at which the two test systems are scanned.