Fetch entities outside of VBO to process with VBO entities

For months now I´ve been trying to figure out how I can access entities outsite the VBO and have a Rules component process the two different entities.

Example:
A node is viewed (a tournament) and I want to register nodes to this tournament using VBO. I´m loading nodes from another content type into the VBO view (participants) and want to create a relation from each participant to a tournament. To display everything on the same page I use EVA or Page Manager, depending on how complex the site is.

Creating other relations between entities with Rules and VBO (e.g. creating attendance lists where I use participants from VBO and a "now" date as endpoints in a custom entity type) is no problem by looping through the VBO list and creating a new entity type as the other endpoint and setting the default value. When I want to use the viewed tournament and pass that into the Rules component where the VBO processing takes place is just out of my reach.

I´ve tried using Page Manager to display the tournament node and a VBO content pane in one panel but I still can´t access the viewed node. The only thing I can process is the stuff INSIDE the VBO view.

I also tried Rules Bonus Pack since it offered a "Variant x is rendered" to access all the entities in the variant but no matter what parameters I sent to the Rules component that VBO runs on submit I could only access the entities loaded inside the VBO view.

I also tried creating a rule with the "node viewed" event and an action where I run the component. That way I can atleast sent the tournament as a parameter to the component. That works fine but I want the user to load the component after selecting the participants himself.

Please tell me your thoughts on this since it´s been months now. I´ve not been willing to submit a support request since it seems such a simple procedure. Why is the viewed node not accessible to the Rules component that the VBO runs on submit?

I was not sure where to post this but I Rules seemed the best place to do so.

Thanks for making Drupal what it is today!