This is not possible and variable interpolation is specific to Nomad job specifications not agent configurations. We expect a configuration management tool to provide this functionality when configuring the machine which Nomad will run on.
An example of why this would not be possible can be seen in your example. The Node.ID is only generated/known once the Nomad agent has started, but it needs the name configuration parameter to start.