I eventually found a solution to this scenario.
I got another copy of the default filebeat-kubernetes.yaml manifest provided by Elastic here: Run Filebeat on Kubernetes | Filebeat Reference [8.15] | Elastic
If you deploy Filebeat as a DaemonSet with the above file, it will use a ServiceAccount, ClusterRole, ConfigMap, under the default filebeat name.
So if you want to deploy a second Filebeat DaemonSet, you would use another manifest file, and edit ServiceAccount, ClusterRole, ConfigMap, etc. to use a name that is different than the name used by the first DaemonSet.
So if you have say 3 software development teams running 3 different projects that are all deployed to the same Kubernetes node, you could set up 3 different manifest files, instead of configuring one monster size manifest file with settings for all 3 projects.
More details here:
Filebeat DaemonSet on Kubernetes not shipping logs - Elastic Stack / Beats - Discuss the Elastic Stack