Right now I am using the 'LocationUpdate' notification type and have an initial implementation of the data receiver/processor. The problem is that CMX sends us individual location items (one per CMAC) at a very high rate (hundreds of requests per second). It would be much easier for us to get location updates in batches every 1-2 minutes (this is how it works for other devices we already integrated, like Aruba and Meraki).
You may use "Movement" trigger instead "Location Update". In this case utilization will decrease.
There is no way to throttle the Northbound notifications as such. You get notified as soon as the event is processed in CMX, we can’t send it in batches. If you go for Movement Notification trigger, you can try to limit the number of notifications by having a higher ‘distance’ value in the trigger subscription.