Self modifying code is a can of worms. Many things can go wrong, and good luck debugging the mess.
As for self-modifying code, the dangers are way overstated IMO. Having written a lot of it as well as reverse-engineered and debugged code using self-modifying code heavily, I look at it as just another tool in the chest. It's pretty easy to chop your limb off using self-modifying code, but having audited a whoooole lot of static code, I'd say that argument applies to just about any tool.
Linux uses self modifying code (usually at startup) to efficiently support booting the same kernel on single an multiple processor machines.
AFAIK the first Intel CPU to have branch prediction was the Pentium 2 -- which was released many, many years (I'd say ~12 years) after the 386.
Therefore if an architecture is no longer needed then nuke it. What's the point of hanging on to 386? I doubt that any new machines today are shipped with 386 CPUs. Even embedded radiation hardened special systems are now having better CPUs, such as Pentium-compatible or some PPC.
And the systems still running are certainly not upgrading to a new kernel.