Again, I see your points and where you are coming from, BUT as for a List of Accounts, that is what the Stored Proc would be providing. My thought is that it would be triggered on a Schedule and each Key Value would be dropped into a Queue (Dispatcher Model).
Then there would be a separate (Processor) Robot scheduled that would pick-up the queue item(s) and process within a transaction utilizing the REFramework.
“but you will get more bang for the buck if you use the bot to do more activities rather than limiting it to a few activities.”…not sure about this statement as the Bot(s) would still be performing a lot of activities. Whether going thru a UI to derive a list of Account Numbers or calling a Stored Proc from with the Robot, what is the different? UI interaction versus Database interaction.
I understand the point about communication in regards to any code changes that might impact the Stored Proc, but the same could be said for the UI also. If a different Team or Developer modifies a UI that a Robot is interacting with, then the same is true.
Overall, still not sure whether one is better than the other as both seem to have pros and cons.