@Alek, when I saw the first few sentences of the post calling this technical, I was excited. However, it still leaves me wanting for more. I find the technical aspect of running a client such as OSBot fascinating, and would love if you were to include more details about engine functionality and how OSBot works with it.
As far as the faux antiban you mentioned earlier goes, the only reason it would be helpful is if the client itself recorded such actions and sent them over to the server. I'm assuming since you make fun of this kind of antiban, no such reporting mechanism exists. However, what if something like that was added in the future in the client? Wouldn't it require all scripts to be updated, or some kind of mechanism in the OSBot client to randomize the timestamps that actions were executed? In your opinion, is this something Jagex might do?
As far as reverse engineering and game hacking goes, my knowledge is very limited, pls no roast. Reading section 5 of your post, you mention injection vs reading memory. Is it safe to assume that because of Java's limited low-level calling abilities, that there is very little difference between being able to detect client modification from the client itself? I'd imagine in an unmanaged language such as C and C++, doing things like computing function checksums, checking for interrupts, etc is a lot easier to do than in a Java client. Do you know if any such integrity-checking mechanism exists inside the OSRS client, either via JNI or a pure Java implementation?