hyp list cluster-stack will list all existing CloudFormation stacks in the user account and region, not only the HyperPod-related ones.
A suggestion for improvement would be to tag the CloudFormation stacks that are created by the CLI and also by the HyperPod cluster console creation experience with a specific tag, potentially also including the template version / commit hash. Then the hyp list cluster-stack could filter for this tag.
A minimal short-term fix should be adapting the --help output. It currently claims that the command only lists HyperPod-related stacks.