LogManager.demandLogger accepts a caller argument which is later used to resolve ResourceBundle. However LogManager.demandSystemLogger doesn't have that caller argument - which could later lead to some inconsistency when resource bundles are resolved.

This is more an inconsistency than an issue since by definition the caller that creates a system logger is a system class in the bootstrap class loader.
However it could become an issue in a modular JDK - where different system classes may come from different modules and where information on the actual system caller class may be needed.