I suppose your issue will be solved with 2.1.0p17 as well.
We found out that the password store issue is linearily related to the number of active checks. More precisely, CMC accesses the stored passwords, decrypts them and so on, … once for every instance of an active check you’ve configured. Given that the BI services are active checks as well I suppose you’re hitting this same exact issue.
Given that the issue is a combination of password store multiplied by active checks, it makes sense that 2 different strategies offer relief: you either get rid of the password store, or you reduce (significantly) your active checks. Anyway, 2.1.0p17 should be out any day now I suppose and we can verify if the issue is solved with this for all of us.