Run Automation Services tasks and Scheduled Updates rules with different accounts

As it is right now we can create Scheduled Updates rules and Automation Services tasks and run those in the server. There is also an Account we can set up (in case of using Kerberos authentication, which we are) in the configuration to run Automation Services in the server and also one for Scheduled Updates. That is all good when there are no personalized information links.

In our case, most of our data is secured with row level security and Information Links are personalized so users can only see the data they have access to. Now, if we configure Scheduled Updates to work with a Windows account, then that account has to have access to all the data in the company so it can upload the different data sets required. That can create a security hole for companies like ours. Automation services has the same issue in this scenario. 

My idea is to add an account to each tasks or rule and have it run with that account. At that point we could say, Report 1 runs or is scheduled with account "X" and Report 2 runs with account "Y" and those two accounts have different level of access in the data. In other words, it is more granular.