There are whole categories of env vars that should be shared across an organization. (Like API keys or credentials for package hosting services like gemfury.)
The Contexts feature is nice but unhelpful for jobs that aren't using workflows.
Related... why does the Import Env Var feature require admin privileges? If I have access to _add_ an env var, and I have access to the env vars of other projects, then by definition I should have access to import an env var from another project (to which I have env var access) into another project (to which I also have env var access).