Populating a PATH env variable using programmatic command substitution $() leads to a literal giant string, rather than tokenized paths

Question

I\'m creating a PATH environment variable that begins with /foo and ends with /bar; and in between I "sandwich" in a collection