Not sure what your actual concerns are.
ISE is predominantly a standards based Radius and TACACS+ server. Any device that speaks stands compliant Radius or TACACS client will be able to communicate to ISE. Radius and TACACS is initiated by the client and ISE will be able to handle whatever the client throws at it.
If you are speaking of visibility, then perhaps you mean Profiling compatibility? I would bet that Device Sensor is a feature that only works on certain Cisco boxes, and not third party. But you can still feed profiling data into ISE via things like DHCP IP Helper forwarding to ISE (any switch will have this feature), Port SPANS, Netflow, etc. Variances might occur with Profiling features like SNMP trap - some switches might not be able to send an SNMP Trap when a link goes up. But again - what is it exactly that you want to achieve?
ISE is not an NMS application that will allow you to visualize switch ports.