Earlier quoted context omitted.
Would calling it a "driver adapter" fit more accurately .. ?
I don't think so, no. It does not appear to be functioning as an OSX device driver. It's just hosting a network print server in docker.
Makes it so if there’s an issue I don’t get a kernel panic
Maybe it could write something CUPS compliant though ?