possible but completely impractical, esp as all buttons/modifiers would need to be toggles and untoggle any other layer change toggle when one is activated. you’d also then not have any modifiers for normal mapping tricks.
with midimasher sitting between the launchpad and traktor you’re only limited to how many ways u can think of selecting page/layer switches and it handles all the 'out’s for you on layer changes - so won’t get tangled up in any traktor issues there.
there is still a limit ofc to how many pages/layers you can map using just one midi device in traktor - but with 16 channels of 128 values and only needing 64 for the main grid that’s a lot of potential pages 
best to leave channel 1 alone as then that can be used to route the launchpad data unchanged so that any normal launchpad tsi can be used on it too, but that ofc still leaves 30 pages that can be mapped, which is probably enough
and ofc, like u said, that can be expanded by adding extra midi devices in traktor, so adding each extra one of those would give an additional 32 pages (as we wouldn’t need to reserve the launchpad default one for any others)
i’ve also created a mapping that uses the arrow buttons to scroll a much larger grid around the 8x8 launchpad one, works nicely for clip launching and stuff, but less use in traktor probably.
i was thinking of making user1 and user2 toggles, that ensure only one is toggled on at a time and when both are toggled off then the launchpad is back into vanilla mode and just routing the standard midi to and from traktor. the right hand column of buttons would light up in red when one of those user1/user2 modes were selected and the current ‘page’ from that bank lit up in yellow and it would remember the currently selected bank so when u hit user1 or user2 again you’d be back on the same sub page you were before.
the real power of using midimasher tho with a launchpad is to also do the actual traktor mapping in midimasher code, makes selecting colours of the buttons for off and on states really easy and stuff like ‘loop’ controls like we discussed on that other thread very simple and all work exactly as they should.
this bit of code creates a shift button and loop controls for decks a+b on page 1 of the launchpad. full led feedback on loop length etc even if the loops are changed in traktor or from another controller, loops are in “hold” mode unless the shift button is also pressed in which case they toggle.
hold_modifier(“lp”, “trkon”, 1, lp_hi_yellow, lp_lo_green, “shift”)
loop_sizes = { “/8”, “/4”, “/2”, “1”, “2”, “4”, “8”, “16” }
traktor.loops(“launchpad”, grid(“6,0”, “7,3”), 1, lp_hi_green, lp_lo_green, “shift”, “a”, loop_sizes)
traktor.loops(“launchpad”, grid(“6,4”, “7,7”), 1, lp_hi_green, lp_lo_green, “shift”, “b”, loop_sizes)
thank you
I’m thinking to update it to 2.5 shouldn’t be much work just to add FX store preset and some new tricks to performance mode.