That's exactly the point I was glossing over when I recommended a dispatch table at the receiving end, and a JSON producer at the sending end..
The OP doesn't have to use JSON, but it's convenient, and well understood. The point is that the OP cannot simply pass references around, he has to pass plain old data. So a JSON packet that looks something like this:
...would be easy to interpret at the receiving end. And the dispatch table avoids the mess of going directly to symbolic subrefs.
Things get ugly if he's got to send huge amounts of data to the subroutines. But even there, an additional layer of indirection can help; instead of sending data as a parameter, send a link to the data; a filename, a row ID from a database, or whatever. But sending a Perl reference is an indirection that will lose its magic as it gets passed around. ...just like you wouldn't pass a C pointer to local data from one process to another.