sounds risky. this system is productive and i am not sure what kind of sideeffects will occure.
anyway, its sounds like a workaround. i would prefer a clean, german-engineered solution, like the asg is

as the asg allready knows the service it seems like little step to provide them to other functions. all this p2p stuff seems to have a inconsistent implementation, ie in qos traffic selectors there are preconfigured selectors. the different p2p selectors seem only to differ in naming.
i think this is done like that, because p2p service have a dynamic nature regarding ports. so call them dynamic service groups. or just follow the half-baked way and add some preconfigured multipath rules with the next update.