That's pretty cool. It would have never occurred to me to try to do a minikernel in bB. I'm not sure that example would be any easier to teach than the assembly equivalent, though.
Anyway, for purposes of my guide, one of my goals is to teach some assembly to experienced bB coders, which, as you seem to be saying, can be useful to bB programmers even if they primarily stick to bB.
I'm trying to think how to put this without sounding like I'm telling you how you should be doing it, 'cause I'm not.
You show some bB and then some equivalent assembly. My off the top of my head, gut reaction is that that's a good way to do it.
The bB gives you something familiar to hang it (eg the assembly) on.
I was just pointing out that you could take that farther.
Now if it was me, I think I'd start with the bB show the how and why of the assembly it produces, then
how it could be improved and how you might do things in assembly that aren't practical in bB
(I'm thinking specifically the bit of code that does the MOD 15 and timing in a loop as a good example).
But I'm not sure that that's better than just saying 'here, learn some assembly it's not that hard'.