So, I think I finally understand why this is happening when our APIs start:
This is not being caused by the huge amount of before/after remote calls in our main API like we first thought. It is instead caused by the amount of multiple before/afteRemotes on the same remote method (endpoint).