Drum Maps is about assigning drum sounds to notes.
The typical ones a drums vi use are General Midi, for example C1 kick drum, D1 snare plain hit, D#1 drag, E1 half edge snare, F1 rim shot; G# for pedal stomp hihat etc... then cymbals, and for a whole kit tends to cover several octaves range. (I use Cubase with the Yahama numbering ("-2" in BFD3) so these so far are C0 etc, and in the range of most of my keyswitches; EXCEPT this falls in the play range of certain bass instruments, and this is out the window completely now.)...
and as such have no particular relation to where you'd want to organize your keyswitches through itself. You'd be going through a process which is unnecessary as you're going to have to make decisions anyway.
"how DM work to actualy change the articulations without placing a midi keyswitch note on the same track as the midi music." they don't, I didn't understand the question.
- nothing that isn't assigned to the MIDI channel the instrument receives data on communicates with it. But you have no good reason to be thinking about drum maps as a go-between, it would be a waste of time.
VSL is pretty consistent with the factory matrices; for example a short and long notes matrice has the lowest KS staccato, then portato short, medium and a sus. For eg., bass flute they start at Roland # C1, Yamaha C0*.
VSL uses the former, there is a way to set it to use the latter or any other known basis in General Settings, the gear icon. The lowest pitch in the play range is *Bb (2 or) 1, an octave and 10 semitones above the low KS, ie., there's no conflict up to there.
So you could take that as a model for organization, it's coherent. I tend to, but I make my own rather ad hoc
rather more