^^ Yeah, that's right. It's more productive to map things on the controller and plugin itself than doing it in Live. So with regard to constantly having the pads mapped to a Drum Rack in Live using Ch16 as I mentioned, you would save the following mapping as a template on your controller:
Then you would just set up a default Drum Rack state in Live with the default pad selection starting at C-2, with i/o set to Ch16 an monitor to In like so:
(Sorry, the MIDI from in the screenshot says "All ins" because I don't have my MPK49 plugged in at the moment. But substitute 'All ins' with 'Your Controller' and it works!)
So with that configuration, you don't even have to arm the drum track for record. The pads will always trigger your drums. And, like Schnork said, setup is a lot quicker. Now the only step you need to take to map your drum track to your MIDI controller is set the track in your DAW to Ch16.
I do the same thing with my control banks for synthesiser patches. For example, I have a default program on the MPK for Massive's macros:
Then I have a default patch in Massive with the macros mapped from CC22:29:
So if I'm working in Massive, I don't even start patching until I've loaded the default patch. That way, doesn't matter whether I'm in a DAW, desktop, on m computer or anyone else's, my keyboard will control Massive's macros exactly the same.
Like when I started using computer MIDI I spent a lot of time using my DAW's mapping controls. But it's such a time sink, particularly if you're essentially performing the same mapping over and over. Now I hardly ever have to use Live's mapping assignments, because I have programs on my keyboard and corresponding patches in over 20 instruments.
Global mapping is definitely a good and productive habit to get into! Do it once and then every time you have an idea just get to work because your controller doesn't need to remapped every time