In reply to Driven5 :
It's... complicated.
In the 1980s, Ford had a somewhat revolutionary concept in the EEC computers, forgetting now if it was the III or IV, called FMEM. Failure management effects mode, or failure mode effects management, and that is hazy too because it's been close to 20 years since I needed to remember things like our local barometric pressure is 155hz on a Ford baro sensor. Basically if a sensor input was determined to be faulty, a substitute value would be used. Because the computers of the time were fairly expensive for processing power, RAM, and ROM, the fault checking criteria and substitute tables were extremely basic, like having a very coarse TPS/RPM table to substitute in if the MAP failed, so the engine would not run "great" but it would still run, with things like fixed timing (easy to do, just stop sending a signal up the SPOUT line to the ignition module) and the like.
Other cars, if you unplugged the MAP sensor or airflow meter, it would just stop running, no value substitution. Again, what Ford was doing seems pretty basic, but revolutionary in the 1980s. Ford's methodology would actually insert a value into the computer in such a way that if you were looking at a scan tool, you would see the FMEM-calculated value instead of the actual sensor input (or lack thereof). If you didn't know that you could chase your tail all day long.
Oddly enough, OBD-II has made this both universal and comprehensive. Because they by law have to sanity-check the inputs, in most cars you can unplug major sensors and the thing will still run acceptably well. Unplug the MAF in a GM and the engine might actually run better GM in particular uses MAP and MAF and alpha-N tables and cross checks everything. All this cross checking means that they will run quite well when there is an input failure and you wouldn't even know it if the MIL wasn't on. It isn't a "limp mode" because the computer isn't limiting anything. Heck I drove a 1.4t Cruze around a bit today with the MAF unplugged and it didn't even turn the light on. There were a billion pending codes for open circuits, of course, but the computer was perfectly happy with just going off of alpha-N/speed density and it drove very well. Must have all been two-trip codes.
There is no government requirement for the engines to not hurt themselves, only for the computer to tell the driver to shut the engine off if it IS doing damage: the MIL must flash if there is a "catalyst damaging event". Mind you, they don't care if you hurt the engine, they just care if you damage the converter, because that will increase emissions in the long-term. A broken engine decreases emissions because it becomes a statue
Hondas can be amazingly dumb. Run a K24 low on oil so that VTEC can't engage, and it won't simply run off of the non-VTEC maps. It will run like complete garbage past where the switchover point should have been.
It's also kind of a good thing, too. Run the valve lash so tight that the valves hang open at light throttle at a range bracketing around 130-140ish F coolant temperature, it will misfire, and flash the light, but when it gets to full operating temp and the lash opens up again and it has reliable compression again, it will hit on all cylinders again. It's transitory.
IIRC, Chrysler was the first to kill injectors with a detected misfire, on the LH cars. Not everyone does it.
Really, when I think of "limp mode" I think of TRANSMISSION control. A lack of control by the trans computer usually meant that the transmission would hydraulically be in one certain gear, and line pressure would be jacked up to maximum. Find a solenoid control matrix for your given trans and look for what gear it would be in with all solenoids off - that is the "limp mode" gear. Usually 2nd, sometimes 3rd. Low enough that you can move from a stop, high enough that you aren't too much of a traffic hazard.