Hi,
You cannot do this (easily). We currently rely on the BouncyCastle Provider. As a starting point to where that JCE provider is configured, take a look at the project (core repo)/org.bouncycastle/ and /core/org.bouncycastle/META-INF/MANIFEST.MF where the org.bouncycastle JCE implementation dependencies are listed. The user interface for that provider (Algorithm perspective) is fueled by bouncy-castle-specific XML that describes the available operations. So, I am afraid you can't just swap out the bouncycastle provider with another.
We are currently working very fine-grained abstraction over the cryptography provider.
May I ask what you try to achieve more specifically, or does that answer all your questions?
Kind regards