Separation CI and CD process in Jenkins pipeline

I’m currently managing a GitHub organization folder using the GitHub-Branch-Source plugin, which automatically creates a multibranch pipeline for each repository in the organization based on a remote Jenkinsfile using Remote File Plugin.

For each repository, I would like to set up a multibranch pipeline dedicated to Continuous Integration (CI) and a separate job pipeline dedicated to Continuous Deployment (CD). My plan is to have the CI pipeline’s final step use Job DSL to create or update the CD pipeline with default values and then trigger its execution. However, it appears that the GitHub Organization Folder only supports multibranch pipelines.

Could you please advise on alternative approaches to achieve this setup?