Shannon, what you're suggesting is prone to the same issue (creating a broken symlink) if a given destination does not exist relative to cwd. I think your current solution is better as it explicitly provides the paths, but it's not generalised enough to warrant a change in behaviour.

If you have anything new to add or would like to add a PR, just post on that issue. As you note, the core developer stated that the current behaviour is by design.