hi Ryan,
Project 1 has Group A in its group ID field (edit the project and search for the word Group). Project 2 does not.
I hope it's clear from this then, that group statuses cannot be hidden from users not in the group. Their use can only be controlled through which group is specified on the project. This also leads to my second obvious statement: only one group's set of fields can be used on any given project.
Best practice suggestion: our project templates should be set with a specific group in that Group field so that the projects created from the template always sport the statuses required for that workflow.