Well your CPU minutes might be excessive because your processes are taking longer to complete, again as Cifra-Patrick says due to overloaded servers which will cause things to take much longer or possibly sleep before they complete the execution.
Not sure how they have it setup, or how your scripts work... but I'd take Cifra-Patrick's advice and try at least another shared plan from a non oversold provider shared hosting plan. If that did not cut it try a reseller or VPS plan. And if that doesn't do it, go for a dedicated.
vBulletin is not that much of a hog in of itself. A shared server should run many many vbulletins without a problem....unless your forums are excessively busy, I'd try what Cifra-Patrick says.
★ GlowHost ★ → Affordable Managed Web Hosting Since 2002.
█¬Cloud Servers- Hot Failover + Clustered Storage
█¬Managed Dedicated Servers - Semi-Dedicated Servers
█¬Shared & Reseller packages - 20 Min Ticket Response 24/7/365
Well I don't think a shared plan can handle 200 vbulletin users at the same time, this is Why I'm looking for something bigger.
Currently, I'm over the limits and average under 50 users online. I have to "throttle" my web site because of that. (stopping publicity)
I'm not really looking to change 5 time of web hoster. I would probably go dedicated and then IF the server is sleeping most of the day, I would downgrade to VPS. But seeing the VB forum, look like it will be the opposite.
Edit: Also on a long run, this server would host 20-30 smaller web site too.
Email me at leclair [at] iweb.ca we will continue out of the thread so we can keep the thread on subject if people have other suggestions. And do not worry, server emergencies are always answered withing 15 minutes 24/7, you can report emergencies through a form in our Customer Hub, request emergency work order 24/7 according to your management package or report emergencies by phone 24/7 following the correct procedure. And the sales staff is not involved in the tech support process. Furthermore, all servers are connected to a remote reboot port so if your server goes dows you can reboot it yourself. If it does not come back you report the emergency through the hub and someone looks at it quickly.