The basic rules for verification throttling are based more on disk latency. The trick is to figure out how long to configure the the verification to "sleep" to lower the latency to acceptable limits.
The first step is to monitor the disk latency during verification. So you'll want to look at the Average Disk/Sec. Read and Average Disk/Sec Write counters. To be in line with Microsoft practices these need to be below 20ms. You will want to look at these counters for each LUN containing the DB's being verified. During the verification time if the latencies are above 20ms then the verification throttle can be adjusted in order to keep the latency within the acceptable limits.