Yes, this should work very nicely.
Three small caveats:
(1) We are not 100% happy with the way we delegate from the GenericReflector to the more specific platform reflector (JdkReflector / NetReflector / "JamesPropertyReflector" ). Ideally it should be possible to have a longer chain of dependancies.
(2) We still have some constructor-checking code in our normal code, which should be in the reflector.
(3) We have code that can "tell" the GenericReflector about the classes in the system. This code is specific to the GenericReflector.
For you this will only mean that you will have to use a GenericReflector that delegates to your reflector and ideally everything should work fine.
If you can a ".NET property reflector" to work nicely, you may even want to post it back to the project area of our website. There may be other users that would also like db4o to work against .NET properties (not fields) and you may get help to maintain the reflector.