The final result of this ZIP does not seem sustainable long term in regards to preventing fee based privacy leaks. As Zcash grows in popularity some developers are likely to ignore the fee recommendation.
Specifically I am building a service that will use the encrypted memo field. My plan is to honor the recommendation of this ZIP. However if my service becomes popular the number of transactions and transaction fees will be substantial. I am greatly concerned that another developer could try build a similar service to mine and undercut me by paying lower transaction fees.
Lets revisit this and create a new ZIP where creating privacy leaks cannot become a competitive advantage. We need a solution that includes protocol level enforcement in order to both product user privacy AND create a level playing field for developers that want to build useful things on Zcash 