Hi, yes it is possible to instrument this using something like a custom script monitor in SiteScope. The default monitor for cpu looks at only CPU usage. For detailed monitoring like this, it is better to go with agent-based collection.
There's a trade-off that you would typically do with remote monitoring vs agent-based monitoring in general. Remember that even if you did do a remote check with sitescope once every 10 minutes you would get only data collected at that instant of time, and so you might miss a spike that may happened earlier within the 10 minute period.
While you can reduce the polling interval, that again increases the logins and logouts on the system - especially on UNIX/linux. there's a definitely a network latency tax.