I'm afraid that there are no plans to backport this to Spring 3.x, since we're not considering any EE 7 level APIs there, and will effectively turn 3.2.x into maintenance mode as of May. Spring 3.2's regular Bean Validation 1.0 support should work even against a Bean Validation 1.1 provider at runtime - with the exception of method-level validation support which doesn't work at all there against Hibernate Validation 5.0, admittedly, since HV 5.0 dropped its old method validation API completely.
As for Spring 4.0's Bean Validation 1.1 support, with the introduction of getParameterNameDiscoverer on ValidatorFactory and forExecutables on Validator, we have a problem with Bean Validation 1.0 compatibility at runtime since both of those methods declare return types that are not available in the Bean Validation 1.0 API. After all, BV 1.0 is hard-coded into every EE 6 server out there, so we have to remain compatible with it: There is no way to override the version of the BV API in such an environment.
Now, with respect to "forExecutables", you could simply accept the LocalValidatorFactoryBean reference as a ValidatorFactory implementation and call "getValidator()" on it: This will return the provider's native Validator, with full support for "forExecutables". Or you could accept it as a Validator implementation and call "unwrap(Validator.class)" on it, which will expose the native Validator as well. This should even work with Spring Framework 3.2 against a Bean Validation 1.1 provider at runtime...