Well it was Google's excuse for how only certain Chromebooks of a recent vintage would be getting Android app support.
Maybe they meant the major version number of the kernel wouldn't get an upgrade, though I suspect maybe performance/memory limitations are the real issue. It may be possible to backport whatever features are missing to an older machine's kernel and see...
https://www.chromium.org/chromium-os/chromiumos-design-docs/...
...and you can manually select between them by using the "cgpt" command from the shell:
So on an ARM device, you could say:
If I'm not mistaken, this would mean to set partition 6 (a kernel) with a priority of 5 (compared to other partitions at boot), successful flag set to 1 on mmc block device 0-- (the internal mmc, where mmcblk1 is the external sdcard). I think if that kernel fails, that flips the successful flag to 0 and it falls back to the next priority kernel on the reboot. But like I said, it's been a while so don't quote me.See more here: https://www.chromium.org/chromium-os/chromiumos-design-docs/...
Also, if you weren't aware, to get into the shell:
if you play with cgpt, be VERY careful. Also, if you're thinking of replacing kernels or whatnot, be aware that on most (all?) devices, the partitions are signed, so you'll have to turn off any checks first.