Not sure that would do. We'd then only run the secure tests with the SecureRpcEngine.
The way I see it: The SecureRpcEngine is more general (by definition). It can run a secure and non-secure setting. It's the one we should switch to and the one that gets the testing.
Maybe another option is to now have a non-secure profile, just for testing. It would exclude the the secure tests and the secure resources (with some maven trickery). That way we could still two jenkins build.
Yet another option is run a select set of with the both RpcEngines. TestFromClientSide comes to mind, as well as some of the bulkload and M/R tests. So almost all tests would run with the SecureRpcEngine, and some would also run with the WritableRpcEngine.
I think I'd favor this latter option.