The problem is not so much with this interface, as it is with commenting out the creation of the ConsoleService objects in DependenciesImpl.java.  Understand that there is more than just one console.  ConsoleService uses ThreadLocal to try make sure that output is directed to the correct console for the thread, but in DependenciesImpl.java, where console output is written by a worker thread, it is necessary to instantiate the ConsoleService object for the thread so that the thread local for the thread will be initialized and console output written by that thread would be directed to the proper console.

ConsoleService references no OSGi classes, so there is no reason that it can't be in core rather than in service.  Only the OSGi specific subclasses of ConsleService.ConsoleWriter (CIConsoleWriter and CSConsoleWriter) are OSGi specific, and these can remain in service.  You could create a non-OSGi console writer for your use case, or perhaps, change ConsoleService.ConsoleWriter from an interface to a base class that writes the output to system out.  Then you can remove println from IPlatformServices and continue to use ConsoleService.println() instead.