Federated identity management using Active Directory Federation Services
ADFS (and any other IDP) are most of the time considered tier-0 or "control plane" security zone or level (cf: https://learn.microsoft.com/en-us/security/compass/privileged-access-access-model). So in theory you could re-use. But the reality is that you probably didn't consider the first deployment as a tier-0/control plane type of asset. Therefore, re-using might lead to service exposure as you don't necessarily know who has access or had access to the service, its dedicated account, etc. If that's the case, I would consider creating a new farm taking in consideration all security recommendation from the start: https://learn.microsoft.com/en-us/windows-server/identity/ad-fs/deployment/best-practices-securing-ad-fs.
There is no limit on how many ADFS farm you can have in a forest. As long as they use different names and URL, you are good to go. The only thing that the farms of a forest share between them is the device registration configuration. But that's rarely use anyway.