BLHeli_32 supports a variety of MCUs, in order to maximize performance and also to handle the current chip shortage.
Unfortunately there is inaccurate and misleading information relating to this circulating in various media.

So to clarify:
All BLHeli_32 MCUs (F0, F3, F4, G0 etc) support the "ByRPM" feature, with Rev32.9 code.
All BLHeli_32 MCUs (F0, F3, F4, G0 etc) support "any" pwm frequency range.
The supported range is determined by the hardware manufacturer, based upon choice of fets, driver, capacitors etc.

You can find BLHeliSuite32 here: https://github.com/bitdump/BLHeli/releases

Or here: https://drive.google.com/drive/folders/1Y1bUMnRRolmMD_lezL0FYd3aMBrNzCig
or here:
https://www.mediafire.com/folder/dx6kfaasyo24l/BLHeliSuite
And the Android APP on Google Play:
https://play.google.com/store/apps/details?id=org.blheli.BLHeli_32
For users in regions where Google Play is not available, you can download the ".apk" file in the
"BLHeli_32 Android APP" folder to your phone or tablet and open it. This will install the APP.

You can find the manual in the link above: BLHeli_32 manual ARM Rev32.x.pdf

Rev32.10.9 testcodes are published in the folder "Loaded startup testcode" and "Plane nondamped testcode". The "Loaded startup testcode" testcode has optimizations for starting motors that are loaded, like is often the case for thrusters or cars. The "Plane nondamped testcode" testcode has optimizations for planes that run nondamped mode. It prevents a small kick when starting up a motor that is already spinning. None of these codes are suitable for multirotor applications.

For more information, check out these threads:
https://www.rcgroups.com/forums/showthread.php?2864611 (for BLHeli_32)
https://www.rcgroups.com/forums/showthread.php?3143134 (for the BLHeli_32 Android APP)