I'm calling the REST API from Python with asyncio/httpx. RouterOS 7.9 on Mikrotik cube pro and cube lite APs.

1) Scan: on multi-radio APs (e.g. cubepro) I don't realize benefits running scan on two radios asynchronously -- it takes about twice the time to complete with two radios versus one radio. I had hoped the radios would scan their different frequencies at the same time to reduce the overall duration to complete scans for both radios. I see the same behavior using multiple CLI windows to the AP running scan commands to the different radios at the same time. Scan appears queued/linear in RouterOS. When calling scan across multiple APs the asyncio/httpx libraries appear to be working asynchronously with the performance increase that would be expected.
Related to scan, I'd read elsewhere to allow 200ms per channel for the duration of a scan. Are there scan duration guidelines for Mikrotik on 2.4, 5G, 60GHz, LTE radios?

2) Monitor: I've observed needing to wait several seconds to obtain stable readings calling monitor using REST (extracting the later readings that stabilize). Is that the result of beamforming? Are there any guidelines for time to wait on different radios when calling monitor (2.4, 5, 60GHz, LTE)?