If you mean DryOS in its entirety, no. That would be a massive project, and for the most part we only care about the inner workings of the OS where they directly interact with some particular feature we want to implement or bug we want to fix.
If you want to reverse engineer some part of the firmware, I highly recommend Ghidra
https://chdk.fandom.com/wiki/Firmware_analysis_with_GhidraGhidra includes an excellent decompiler, but useful reverse engineering still requires substantial human analysis.
We do also do a significant amount of automated analysis with the sig finders (finsig_* under tools in the CHDK source) to identify functions and other aspects of the firmware, recorded in stubs_entry.S and funcs_*.csv in the platform directories.
