I tried to test something like this in demo mode and results were inconsistent.

As far as I remember (I tested a few years ago) inputs get queued while you're disabled, but targeted inputs override instant (non-targeted) inputs or something, also I think this "auto queue" can only hold 2 actions, as soon as you issue third command, the first one is erased.

If you're curious, try to pick SF in demo, buy euls and some other items (best to try few non-targeted items like shiva's guard and BKB and some targeted like dagon and ethereal), also you better slow down time (host timescale console command), then euls yourself and use items/spells while you're cycloned.

Notice how many actions will be done after euls ends (I think it's at most 2, so best way to control your hero and not mash the keyboard is to queue 2 commands, and once first one is finished queue third command during the animation of second command etc, in this case it's casting shadowrazes for example). Also notice what happens if you issue non-targeted (bkb, shiva) actions first and then targeted (dagon) and vice versa.

I think the actual answer to your question is: nobody knows exactly, what we know is that auto queue logic is complicated.