Part of the problem may be what Honda reports through the ECU.
With the Query/Response configurable gauges it my be possible to "ask the right question" of the ECU to determine if it's in lean burn. Then we would just need to sit down with Ron and figure out how to program up a custom gauge that takes the mixture into account.
For what it's worth, the Prius has the same problem. Right now SGII calculates fuel consumption using two variables, RPM and engine size. On the Prius when the RPM drops below 1000, the injectors cut out. You can get the car to do this at 60 mph if you have strong 6 bar SoC. Problem is that SGII doesn't account for the fuel-cut.
Might have a same query response answer.
boolean fuelCut = QUERY_RESPONSE();
uint rpm = RPM_GAUGE();
uint gph = GPH_GUAGE();
uint mph = MPH_GUAGE();
// Yes... 9999 is no good, but this would give you a fun iMPG guage to track fuelcut.
if(fuelCut) {return 9999;} else {return mph/gph;}
Now from talks with Ron, I didn't get the impression that the gauge programming would be that complex, something more like AND / OR / NOT. The solution would be to have fuelCut return 0x0000 or 0xFFFF, then to use that to AND with gph, but then you'd have to figure out how to handle div-by-zero.
Point is, if the right instructions are available to program the custom gauges, only one guy has to figure out how to do it, the post it on this thread...
11011011