I work with drum parts in Step Sequencer all the time, and at the moment there are some weird things that can happen if drum maps are used with step sequencer, so I too have to deal with note names/numbers like you do.
What I ended up doing was to build a Word document that has a table in it where I pu in the note names and numbers, as well as the associated general midi mapping of drum kit pieces that get triggered for each note.
I then use that document when creating drum sequences in step sequencer, and it seems to work pretty well.
When I create any custom kits that do not map as general midi maps drums, I also then create a Word document specific to that custom kit's mappings, and I use that then when I am sequencing drums in step sequencer.
It doesn't take but a few minutes to create such a document, and for kits that map to general midi drum note values, it is quite easy to begin to learn what notes play which drums. Creating similar documents for custom kits also does not take much, and having that document handy when sequencing the drum parts for those kits makes that an easy task, as well.
I hope that helps - from a different thread, Dan from Cakewalk has been looking into some of the reported issues using drum maps with step sequencer, and if they ever get that stuff all working like it is hoped, then you will be able to use drum maps and not have to guess any more.
Until then, try the method I describe above, and maybe that will do the trick for you - for now.
Bob Bone