It's difficult for me to talk in terms of SQLite or Linux system libraries, but under Windows, it could mean, for example, writing an .scm library that would interface with user32.dll, gdi32.dll and opengl32.dll APIs, define a set of high-level macros and procedures on top of them, and using this library as an OpenGL-capable windowed GUI with standard forms, controls, dialogs and what not instead of that crooked Java trash Rob was polluting our gear with.
Tell you more, single-threaded nanoscheme/OxyScheme are my minimal extensions to the Public Domain code that was used to develop multi-threaded TinyScheme as we see it now. In fact there's very little difference between the two if we put aside the common access conflict prevention trickery that TinyScheme is full of. Theoretically there's nothing that can basically interfere if we choose to expand the nanoscheme/OxyScheme project into a full-blown microscheme/PeroxyScheme multi-threaded monster based off of TinyScheme sources.