Does it make sense to improve abstraction layer inside Xith3D such a way to be configurable which implementation of logging to use? In production build I do not need any logging, so I'd like to detach logging from my app at all.
Yes. Many people will not only want but need logging in a production API - the main logging API's (log4j and java-logging) were both specifically designed NOT to be removed from production builds.
However, it might be worth guarding EVERY single logging call in xith with a boolean if test, as discussed in the performance sections (IIRC it was Mark Thornton who reported success using this to dynamically compile-out logging at runtime - personally, I've been using it for years to be able in extremis to make builds which compile-out logging, e.g. when I don't trust the logging API
OTOH, if you're not stupid, then the logging API's really are very fast.