Hmm, except in the 100% of cases where it does make sense.
If it is a small customer that is going full stack Meraki, I generally agree (unless they have a compliance issue or special use case). However, there are many customers that already have ISE deployed for their traditional wireless and wired networks. We have deploy a hybrid Meraki / Cisco solution quite often. One scenario is maintaining Cisco switching at all sites, and at times only deploying Meraki in smaller branch sites. We have also had customers that maintain Cisco wireless in their larger sites and deploy Meraki wireless in branch sites with no IT support. I am sure there are additional use cases that could occur in the myriad of customer environments that we all encounter.
In scenarios such as above, the customer often wants to maintain a consistent network policy across the enterprise. I don't believe anyone would argue that the Meraki alternative to ISE is as fully featured, nor should it be considering the cost differential and the Meraki model for product and feature development.
There must be a not insignificant number of customers that have requested ISE support with their Meraki deployments, for Meraki to invest the time and effort in enhancing the integration of the solution
Regards, Jason