Yes, although their scopes are different. For Linux it started as a simple virtual machine for programmable firewall rules. For NetBSD, it's more of a playground to try ideas in kernel space, while rump kernels allow to try kernel ideas in user space.

What are the limitations in terms of what the interpreter has access to? Can it interact with devices, physical memory, etc.?

It has its own memory namespace, so it won't be allowed to access the kernel memory. It has however full access to the devices.

The /dev/lua device, which allows interaction with the kernel interpreter: https://man.netbsd.org/lua.4

Presentation: https://www.netbsd.org/gallery/presentations/mbalmer/fosdem2...