how to have a bpatcher that can save presets for its parent patch.

I have a number of different bpatchers that do different things, i.e. not instances of the same .maxpat, but different ones - i'll call these MODULES (MODULE_BPATCHER_A,B,C,D etc.)
And for each module I want to be able to manage presets in a particular way, i.e. they each share an identical UI to load/save presets, also a dropdown which is automatically populated with the contents of a folder (different for each module) etc.

I have a small network of nodes that do this preset management (load/save/populate dropdown box with contents of folder etc - attached at the bottom of this post) and currently I copy paste this into each of my module bpatchers (which also each have an autopattr), and it works fine. But of course maintaining it is a PITA. Is there a way I can have this custom preset management network in its own bpatcher, which I embed into each module? (i.e. to tell the preset_bpatcher to store everything from one level up, and then recursively down again).

this is what I currently have:
MAIN_PATCH
....MODULE_BPATCHER_A (contains my presetmanager patches copy/pasted straight into it)
....MODULE_BPATCHER_B (contains my presetmanager patches copy/pasted straight into it)
....MODULE_BPATCHER_C (contains my presetmanager patches copy/pasted straight into it)
....MODULE_BPATCHER_D (contains my presetmanager patches copy/pasted straight into it)

this is what I want:
MAIN_PATCH
....MODULE_BPATCHER_A
........BPATCHER_PRESETMANAGER
....MODULE_BPATCHER_B
........BPATCHER_PRESETMANAGER
....MODULE_BPATCHER_C
........BPATCHER_PRESETMANAGER
....MODULE_BPATCHER_D
........BPATCHER_PRESETMANAGER