You're basically saying the name of a command or, of an identifier, is clearer than a switch because the name is much more meaningful, and that I agree, but switch usually have their letter based on the function done by that switch, both versions are readable...
If you argu that 'tokenize 32 $sockread' is better than '/sockread -t32 %name' because -t32 tells you nothing, well what about $sockread?
Considering mIRC never had anything similar, I can easily argu that $sockread is as confusing, as less known, than -t32, both would arguably be looked up.
Now, in the examples, you see $1- being used, there is no $1- inside the on sockread (or sockclose) event, so somewhere, someone tokenized.
Like I said $sockread doesn't say much about how the line was read, where /sockread -t wouldn't change the way a line was read.
This $sockread suggestion is entirely independent of this current suggestion and would require much more work to do a simple /tokenize on the result than -t would, and it could be used to read anything, it shouldn't be added just for this tokenization thing.
Yes your way is just a different way, but I just pointed out how it's not better.
If we had both right now, I'd use /sockread -t32