It's the same. maybe a little more stable when in CTRServer mode, that is much more unstable than normal use.
The problems during the boot, on the base of what I understood reversing the code, depends on the way the cache is invalidated before hacking the interupt vector to get arm11 user mode code execution.
Code:
bl func_00000a70 @ ClearScreen(Black)
bl func_00001a1c @ ARM11_Exploit -> this always work (cyan screen). If it would fail the top screen will be red.
bl func_00000b9c @ Clear and invalidate cache. Here is where it hangs
movs r0, #255 @ 0xff = white
bl func_00000a70; ClearScreen(white) -> It worked :-)
The funtion that clear and invalidate data cache isn't the problems, it's called several times before. So i think that it's how the Interrupt hack is performed.
If you have other information them are welcome. otherwise please stop of arguing on thing you don't understand.