Hi JK,
I can understand the frustration behind this, but there is no any specific standard or benchmark to design the dashboards, all you want is to keep the dashboard simple, quick and meaningful. I can tell in generic that the no of connections is ok, when you say 35 charts think about the data rendering to the chart and the subsequent components too. Dashboard is adviced to not go more than 512 rows and you are taking almost 900 rows and 100 KPI's. Let me tell you this is going to be huge and easily you are going to fall in trap of performance may be not now in future of after 5 - 10 months depends on the data increase.
Why can't you break the dashboard into pieces and use it can used quick as well, I have worked the similar situation like your but not upto 35 charts nearly 15 of mine connected to BW and ending up to fail, later we decide to break up the logic and analysis. I am not trying to scare you at the same time you need to understand the flaws when you design the dashboard. I can tell you one more time dashboard meant for summarized data not for detailed data by using 35 charts.
Using Tab-wise to differentiate and designing the dashboard is helpful, but still all everything is invoked and involved behind. All you can do is make a clear dashboard and separate the triggering operation only for the specific analysis this can reduce the performance.
Dashboards (Xcelsius) General Best Practices - Business Intelligence (BusinessObjects) - SCN Wiki
--SumanT