Sorry, but those do not affect server processing load at all. Server load is impacted by processes that the server has to do in order to construct a page before sending it to the browser that made the page request. Things such as calculating information to be displayed in the members' profiles being displayed in a thread, or information related to viewers of a thread, forum, or page is what can bring a server to it's knees with a lot of concurrent page requests. Searches, especially, are highly resource intensive operations on any server.
On the other hand, records simply stored in the database only affect the remaining storage capacity of the hard drive(s) in the server and don't affect anything at all related to loading and throughput if they are not directly involved in actual processor, MySQL processes, or I/O. If a requested page does not need a record in the database, then the records not being accessed do not affect the processing to generate that page.
So in a nutshell, when some people complain about slowness, I can either choose to ignore it, or I can try to figure out how to alleviate the problem. Which would you rather me do? If I look into it, SOMETHING has to give somewhere to try to streamline the processing done by the server. There are NO free lunches with this.
Quite simply, some functions that are process intensive just have to be disabled as overall traffic puts more and more load on the server. Being able to see who is actually viewing a thread or forum may be interesting, but if it helps reduce server load, I think we can live without it. Honestly, I really don't even want to think about another server move quite yet. So I will do what I can with what I have.