Have you looked at how this will be organized when it’s moved to OpenJDK?
Move what to OpenJDK? The GraalVM implementations of JavaScript and Python cannot be moved out of GraalVM.
it might be that things would be easier if GraalVM wasn’t accessed through JSR223, and that support for GraalVM was made directly in code instead, as an alternative to JRS223.
I assume “code” above means “core”. Currently GraalVM is installed indirectly, when an add-on uses it — MQTT/HomeAssistant, JavaScript or Python. org.openhab.transform.jinja is also a candidate for GraalVM in order to use the Jinja Python implementation, as MQTT/HomeAssistand does, instead of jinjava.
openhab-core provides the necessary interfaces and the add-ons fit there. Integrating GraalVM somehow directly in openhab-core would increase additionally the size of openhab-core with services, which might not be needed by the user, but the user will have to load the services anyway when starting openHAB. The question is rather to move more things out of openhab-core into add-ons: as all the .ide bundles together with the Language Server, or the DSL implementation itself.