Not computing.
Readiness? What is?
Roughly speaking, inside the EFI ECU the computer has a series of bits and counters, and a series of programmed tests associated with each bit. Periodically it runs the programmed test on the system in question (e.g. your evaporative system or the EGR valve). If it passes the test then it sets "readiness" for that test. If it fails the test then it clears "readiness" and usually starts a counter, and when the test is repeated again, it either sets "readiness" and clears the counter if it passes or increments the counter. When the counter reaches a certain number of test failures in a row then it sets the trouble code for that failure and you get a MIL "check engine lamp" on the dash.
If the system is working perfectly then "readiness" will be set for all of the emission subsystems. If there is something potentially out of whack then there will be a pending code (your MIL is not necessarily on yet) and "readiness" won't be set. If the computer finds that the subsystem repeatedly fails then you'll have that orange MIL on the dash and "readiness" won't be set.
The reason they do this is to minimize the number of nuisance MIL's for systems that are subject to normal fluctuations. Evap system due to temperature/pressure variations in the fuel tank, misfires because the occasional miss is somewhat normal, plausibility checks for sensor range (e.g. if the throttle is showing the throttle closed then the mass-air shouldn't be indicating an airflow corresponding to full throttle and vice versa), etc.
There are many other systems that are either working or they aren't, the test is "is a signal being received", and if the answer is "yes" then it sets "readiness" and if the answer is "no" then there is an instant MIL. Not receiving an electrical signal from a sensor is one such example. If you forget to plug in your mass air sensor, that's an instant MIL and an instant "readiness not set".
OBD-II is extremely sophisticated ... there is A LOT of programming in that ECU! Every time it runs a test and the test fails, it memorizes all of the relevant conditions so that a technician can see later on the circumstances under which the code is being tripped ...
Regarding chip-tuning, the reason that SOME aftermarket chips or ECU programs could be trouble is that the way they prevent the MIL from coming on is that they simply disable the function test for that code. If it never runs the function test then you'll never get that trouble code and the MIL will stay off ... but it won't set "readiness" either. You, as the user, would never know this unless you scan it yourself with a scanner that is smart enough to look for this!
So what will happen with cars that have no OBDII?
Everything (almost) since 1996 has OBDII. I don't know what they're planning for older cars. They'll probably just use the idle test that they've been using up until now. There are not all that many pre-1996 cars on the road any more. Some 1996 and 1997 VW diesels don't have OBDII, in fact, some of them don't have any engine electronics at all! (1997 was the last year for the old mechanical-fuel-injected VW diesel) But those are an automatic pass if they're not belching black smoke at idle ...