I'm afraid I currently find the jClouds code base pretty much impenetrable (I haven't had a lot of experience with dependency injection) so I couldn't be sure from what I've ascertained so far.
As far as the core portions are concerned, I suspect you are not alone in this respect. The mechanics and complexity of Guice bindings aside, you will indeed find that a lot of functionality is represented in replaceable strategies and functions.
This makes it easier to override and customize logic for specific providers (especially ones that inherit from a base API but need to make just a couple of small tweaks to the logic), but makes it harder to find the code that actually "does the stuff".
Please feel free to ask questions about how things work on IRC! You'll hopefully find that the jclouds crowd is very happy to guide and explain...
Good luck! ap
