Provider-hosted app timer jobs with app-only authentication - multiple instances with same AppId?

We are about to deploy a timer job (console application .exe file) as a provider-hosted app in an on-premises SharePoint 2016 environment.  It will be scheduled as a remote timer job by creating a Scheduled Task on the provider-hosted app server, which will run the .exe file.

The console app uses app-only authentication.

Is there anything stopping us from scheduling multiple, possibly even concurrent tasks so as to "scale" the job to run multiple instances at once?