Just experimenting on a PC, one can disable all the xrite stuff in start-up and task scheduler, and set the xrdd service to manual (not automatic). i1 profiler then grizzles that it can't find the device, and you have to start the xrdd service manually (and kill it afterwards unless you want it to continue running).
All the while it's running - on my system, anyway - xrdd.exe is using little cpu and memory (16M) but generating around 1,000 page faults per second. In the two or three minutes I've had it running it's clocked up 120,000 I/O operations. Not huge in the great scheme of things, but clearly not good programming to use any system resources at such a rate every second, for a device that's probably used no more than once a month.
Xrite are shining proof of the principle that companies can create good hardware or good software but very rarely both (Apple being one of the few exceptions). I also have a Colormunki Display, which uses different software, and the installer for that is defective and fails on some (perfectly sound) Windows configurations. It ends up loading the device driver 6 times - creating a restore point each time - during every installation on affected machines.