Benefits of AWS Patch Policy over existing solution

We recently deployed a custom patching solution using AWS Patch Manager in the multi-account environment. This devops based solution is on lines of below solutions from AWS. This is a new landing zone environment and the patch management solution is still evolving

https://aws.amazon.com/blogs/mt/scheduling-centralized-multi-account-multi-region-patching-aws-systems-manager-automation/ https://docs.aws.amazon.com/prescriptive-guidance/latest/patch-management-hybrid-cloud/design-multi-account-region.html

Given AWS has recently launched a quick setup based approach of deploying Patch Policies (see the link below), I am wondering if this solution has any merit over what we have in place. Given our existing solution still not 100% ready, I was wondering if there is any benefit of using Patch Policies for managing multi-account patching.

https://aws.amazon.com/blogs/mt/centrally-deploy-patching-operations-across-your-aws-organization-using-systems-manager-quick-setup/

Can anyone provide some guidance here?