Here is why Nektarine NEEDS the option of patch based mappings

[Goschie]

Nektarine is the VST wrapper that Nektar panorama p/t series controllers use. It basically allows custom menu programming and midi assignment programming for any VST, and allows multiple VST patches for layering as well as effects. However and intuitively, the menu programming and midi assignments are per plugin, not per patch; this makes sense for 99% of VSTs, because you are treating them as individual devices of virtualized hardware. But when it comes to rack style plugins (like the Reason Rack) or anything else that allows you to add to the devices list of available controls, the behavior of having maps on a per plugin basis is a limitation. Rather, you would want to save those "rack like" devices as a patch, and have a mapping for each patch, because a patch for a rack vst is more than just a configuration of parameters, its a configuration of exposed midi controls.

I think this could easily be done, as it would be a matter of Nektar changing the code so that if say a button is ticked while saving the patch, a new instrument becomes available to map and its name is the plugin combined with the patch name, and the instrument in the patch is replaced with the renamed clone created in the list of plugin mappings.