Native MPIO for Windows Server 2012 vs PowerPath VE 5.7

A question came in from the field regarding Failover Policies available for Windows Server 2012 on VNX, and the additional capabilities that are available with PowerPath VE 5.7.

To open the scope of the conversation, I'd like to ask for validation of my understanding of the Native offering vs. PP.

The E-Lab Navigator Windows Connectivity Guide has not been explicitly updated to speak to Server 2012. However, the available guide describes the behavior of the Native DSM on VNX (starting on page 318). It is my understanding that the behavior is relatively unchanged from 2008R2 for Native MPIO.

• VNX series and CLARiiON devices will report a default Load Balance Policy as “Round Robin With Subset”, where all paths to the SP owning the device as “Active/Optimized”, and all paths to the SP not owning the LUN as “Active/Unoptimized”.
• VNX series and CLARiiON devices attached to the host in ALUA mode (as is required when using native MPIO) report the path state which is used directly by the host running native MPIO and cannot be overridden by changing the Load Balance Policy.

The PowerPath 5.7 Product Guide lists the policy options for 5.7:

https://support.emc.com/docu42958_PowerPath_Family_5.7_Product_Guide.pdf?language=en_US

It covers Load balancing with PowerPath, Automatic path failover, Application tuning, etc. The available policies with powermt appear to be:

• Adaptive – load balancing and failover policy – IO is assigned to paths based on algorithim that takes into account path load and device priority
• Clariion Optimization – same as above, only for VNX and Clariion and is the default
• Least blocks – load balancing is based on number of blocks in pending IO – based on queuing.
• Least IOs – based on number of pending IO – assigned to path with least IO regardless of block load
• Request – uses one path for all IO – its like there is no PP/similar to native
• Round Robin – Rotates path
• StreamIO – For each possible path for IO to a volume, this policy selects the same path as was selected for the previous IO unless it exceeds a threshold value. If threshold is exceeded, uses the algorithinm to pick a new path
• Symmetrix Optimization – only for Symm. Takes everything into account and is default for Symmetrix

Am I missing anything here? I'd like to make sure that my understanding of the Native DSM is complete when communicating with the field. Thanks in advance for your help!