Re: Paths and Translations...

Turning each alias into a bucket holding language-specific values would indeed be consistent and in line with multilingual fields as well as configuration values in D8.

I'd also guess it'd improve the UI in many places, since we'd be able to  expose the path translations as a. single set.  And of course, when updating an alias, hooks could appropriately act on all aliases in the set.

So yes, at least creating an issue for this would make sense.