What mspape is saying is not clear to me.
"oddly, the humanize settings are locked to the particular slot)" I don't understand this. It's odd? What would you have it do? "it doesn't always select the first and only slot in the patch"...
Do you mean a cell in a matrix? A patch is an articulation, which you put in a cell. A slot is something else, a cell fills a slot vis a vis other cells in the slot fader area. 'only slot in the patch', doesn't make sense. There is nothing to go to or come back from. It might be that this is odd out of your confusion. If you meet the terms for a switch of cells, it happens, it isn't broken. Now, sometimes the network or just the computer isn't quite responsive and a switch is missed, but this 'doesn't always select'... is not a real problem in itself.
& then the 'can it be automatically selected?'
Through the fact of 'it' being the first cell, it is a default, I guess you mean... Well, there are two ways of making, for instance, keyswitches: 1) is not latched, which means you have to hold that key down throughout the time you want that articulation, or it reverts (at note off) to a default. VSL is using latched. I think it has been determined that's what the end user prefers; in my assessment it's simpler.
I don't know how involved a default speed to revert to per that paradigm is for a sample player, but it seems like a lot and I'm kind of not seeing any demand.
If you want speed to bring more variance or error in intonation, it's
quite simple. You go to the cell that's going to be triggered by a
faster speed and put a humanize preset in it. You set the speed that
selects that cell, you go to a next note in a measured amount of time
that exceeds that and the cell is triggered, and there is your
particular humanize setting if you have made one for that cell.
Now, it may seem tricky in your expectations of 'speed control', but it works through calculations at Beats Per Minute. If your first slot is triggered by 'less than 40 BPM', this has to be the relationship from a note on to the next note on. I don't find it very useful myself, tbh. If, in fact, your change of speed is detectable this way, you have the humanize settings 'locked' to the cell and a way of working.
There is no midi trigger to the humanize preset itself. That would be a different design and I don't think it is feasible to expect a rewrite. "the speed parameter ... to work as a midi controller", well speed is_not a midi controller. This is a design of this software; this, 'speed control', may be scripted into other interfaces as well, but speed is not part of the midi protocol. You already have what I think is possible; speed does work, you exceed the difference in terms of BPM from note on to note on and the new cell happens and it has the humanized intonations. :shrug: