Capture more of the kernel spec in the notebook document

The kernelspec name and display_name are currently the only pieces of information captured in the notebook document about the kernel and environment in use when the notebook was last saved. Has capturing more of the information available to the kernel spec manager ever been considered?

I ask because info such as the command used to launch the kernel and environment variables can be useful in studying what configuration was used to execute a notebook document. For instance, knowing the binary executed by spec name "my_special_kernel" is more informative than the name alone.

I do see that blindly copying everything from kernel.json files or the equivalent into a notebook is a non-starter: there might be secrets or other bits of information users don't want captured and leaking out with their shared notebooks. That said, capturing a subset of the information might be possible.