Thankfully, I don’t think the module system changes are going to sweep in and invalidate the above motivating #[path] example for at least a few months, although you’re right that the timing isn’t great.
It’s also the only use I could find which doesn’t involve defining a macro (which would be a bit of a distraction), although I guess it’s not totally unreasonable to have #[export_name = env!("CONFIG_VAR")].