I am not an expert by any stretch of the term, but I can offer my two cents on how how you would generally set up such a system.
It sounds like you’d simply want to make variables- probably just simple boolean variables- to turn blueprints on and off, or to spawn them in and out on the slave players client. The master would have a UI that is tied to those variables- some kind of interface that lets him/her switch or adjust them.
I have next to no experience in programming a multiplayer game myself (I’ve only ever dabbled in single player experiences), but I imagine you would have an instance of the game running on each device, and you would be transmitting those boolean variables between them. Since it is PC and VR, you might have to do something special like creating the experience as two parts (PC part and VR part) that mesh and communicate with each other in real time.
I guess in short, you would use a single blueprint to manage the variables you are transmitting, or you would fashion the blueprints for each gimmick to work across two communicating devices.