Hi @Phil_Seeman , thanks for letting me know 
I also see that there’s a feature in development somewhat related to my use case : the-ability-to-hide-custom-fields-applied-to-a-task-that-dont-belong-to-the-project-in-which-the-task-is-being-viewed/79740/2
I would also like to add to my feature request that if there’s a way in which field level access & visibility(Create/Edit/Read/Delete) can be configured based on user/role , that will be helpful and eliminate the need of multihoming and creating different projects for same use case.