Match across services for different persistent profiles

I read the article you linked to.

Under Match Across Services the two configurations are exactly your situation.

Also, "Important: The Match Across Services option uses only the node IP address to find a persistence match in pools other than the one for which the persistence record was written. This deviation from the normal persistence matching behavior is required to accommodate the intended use cases for the feature to match even when the service port does not."

So, even if each VS uses a different persistent profile, the match will only use the node address.