Hi Hector, it is possible to pass an array of details for each job you wish to create. This could be an array of json objects or an array of arrays containing the details you wish to update. Your best bet will be to use Create Job per Array like you mentioned to create a job for each change, and then as preprocessing for each of those jobs, update the corresponding job or extended properties using Arcade expressions for the output values with the Update Job Properties step.
If you're using the Extract Changes endpoint, and there's anything you aren't able to include from that response, it may be worth querying the feature service as well in each job for those additional details based on the object ids with changes. If there's any information in the scheduled job that you wish to be accessible within the newly created jobs, you can also make use of the parent-child relationship to pull that information. Hopefully this helps get you on track, but if you need further support be sure to let us know.
For anyone at 11.1 and using either a hosted feature service or non-versioned referenced feature service this process is a bit easier. We have introduced the ability to create jobs with feature service webhooks that should cover this use case without needing a scheduled web request. This blog helps outline how to get started with those: Using the Feature Service Webhook Extract Changes Option in ArcGIS Workflow Manager