I had earlier reported that the guide rate of v2.1 Beta has improved substantially that you can now get 2 FPS guide capture rates without having to resort to Bin x2.
Since the TestFlight release notes also mention video rate having improved in v2.1, I decided to measure the frames per second (FPS) from some of my non-cooled ZWO cameras.
The tests are done using ASIAIR V2.1 Beta (Build 9, Firmware 10.66), using a fourth generation ASIAIR (also called "ASIAIR Plus," same as the third generation, but the 4th generation ASIAIR uses a RockChip processor instead of the Raspberry Pi Compute Module 4).
Exposure is set to 5ms so it will only be the limiting factor for FPS of two of the cameras here. The storage is a Samsung T5 SSD. Capture mode was set to AVI only.

All cameras are USB 3.0, except for the ASI220 mini, which we know is a USB 2.0 camera implemented in a USB-C connector. It struggled at 1080p ROI.
For memory intensive sensors, the external SSD clocked in just a little faster than the internal eMMC storage. The ASI294MC ran at 16.8 FPS with the Samsung T5, while it ran at 16.3 FPS with the internal eMMC storage, for example. A faster SSD may or may not be any better than the T5, since it depends on the USB bus.
As to be expected, a Bayer camera (ASI178MC) and a Monochome (ASI178MM) camera came in with exactly the same FPS, so only one of them is listed above.
With a 5ms exposure time, I suspect that the ASI174MM and the ASI678MC are limited by exposure time. I.e., a 1 ms exposure might result in a faster FPS.
The ASI678MC is a surprise, the 197 FPS at 480p ROI is not a typo.
Chen