The limit of activity chaining

Hi, understand from the documentations that the limit of activity chaining is < 50 nodes. Want to understand if the limit includes the nodes within synchronous sub-processes? Also what if the sub-processes ran multiple times? 

For e.g., parent process has 40 nodes, including a synchronous sub-process with 15 nodes. Does that mean that somewhere along, the activity chaining would break? 

What about this other scenario - parent process has 20 nodes, including a synchronous sub-process with 10 nodes but it runs multiple times (let's say 4) - would activity chaining break in this scenario as well? 

For some context: We are trying to implement a search feature for our client that requires the integration between 3 APIs... in our interface we are using a!StartProcess to trigger a process model and using processInfo to get the process variable to display the results of the integration. But ofc our process model is too large (with each integration as their own sub-process that has to be synchronous and some of them having to executed multiple times with MNI configuration) and before the results can be processed, the activity chain breaks and the interface is returning no data to the user. Understand that activity chaining is not traditionally used in this manner therefore we are also acceptive of other suggestions to solve this issue! 

Please advise :"""""""""""")