Hey there @muppetdingdong ;) Thanks for taking the time to upvote and comment!

This is a great question - while we cannot comment directly on future inclusions to Exodus, I'd be happy to at least explain the challenge with adding PrivateSend and z addresses to Exodus in its present form.

zk-SNARKs is actually a very resource-intensive method of sending coins. Generating a z address in Zcash used to require a minimum of 8GB of RAM! It's my understanding that this requirement has gone down a lot since the Overwinter upgrade, but it's still a pretty "RAM hungry" application.

As such, z address generation would change the resource requirements of Exodus and require a lot of UX considerations, as ZEC would then operate completely differently from any other asset in Exodus. Furthermore, z addresses require a full node to use properly, which comes with a lot of extra considerations on the back-end as well.

While we'd love to be the first to market with a z-address compatible light wallet client, there's good reasons why no one has created one yet ;)

PrivateSend also requires a full node to interact with DASH's MasterNode system, and like Zcash, would also come with a bevy of new UX concerns. For example, one would have to set the amount of mixins in the wallet directly - a big design and user experience overhaul, to be sure!

Even the official DASH light wallet client does not include PrivateSend:
https://docs.dash.org/en/latest/wallets/index.html#dash-electrum-wallet

In short, these advanced privacy features really do require full nodes to work as intended and Exodus is designed specifically so you don't have to download the entire blockchain to use it. While it's certainly tedious and not ideal to maintain multiple wallets like this, full nodes really are your only option for private transactions in DASH and ZEC.