Hey @curious7,
This is more of my own opinion but there can be certain polices that can be applied based on the SKU the function app. Mainly because some policies just aren't applicable.
For Isolated V2 SKU, you can apply policies to ensure that resources are deployed in a way to meet specific requirements of the SKU. Bear in mind, Isolated V2 is hosted within an ASE, so by default, it's already highly scalable and isolated. So, policies suitable would include would be those related to compute isolation.
For Consumption/Dynamic SKU on the other hand, would have policies that more adherent to scaling and performance. In addition to controlling, say the maximum number of instances, you would also have policies that manage the configuration, enforcing long-running operations, and dedicated resources of your function app.