Sorry if I am a bit offtopic with this but I wanted to confirm your suspicion about the more complicated pages taxing the system. I do understand that you may want to see detailed information on as much as possible on one page but this is the reality of the product.
The problem is - most web parts used on dashboards or other pages is actually a report that in general runs when page is (re)loaded. If there are many such web parts (= many reports) on the page, this is going to affect ServiceDesk and SQL Server.
We have seen some questions about why the page in portal loads very slow. Mostly these have been about technicians' landing pages - My Task List or Tickets with some added reports on them. I have had to advise removing some reports from a page a number of times. An example - there was a historical Closed Incidents report/web part on My Task List page that had thousands of rows in it which was loaded every time the page was opened.
It is very difficult to give a good advice on this, I guess it is fine to create pages with as much complexity as your server can take. If you start to see performance issues (SQL timeouts, deadlocks when loading the page or users complaining that page takes long to open), make the page simpler.
On the other hand, if the page is rarely used and load time is not a problem, complex page should be fine.
Also, I believe IT Analytics with ServiceDesk reports pack may be helpful in this regard.