The most feasible way of doing this would be for them to frequently do live updates (like you'd see on a Google Doc), rather than version controlling. Otherwise, there's too much potential for code collision.
Unfortunately, Blue Prism isn't exactly the most efficient at doing its transactions, especially if the resources connect to the controller before they go to the DB. This would also require a redesign of their version history system. Probably the only way around that would be to introduce a secondary master/slave system, but that's probably way too complex for them to implement.