Excluding data on demand for specific/manual reloads

I am very excited that end-to-end scheduling has been implemented by means of ‘data on demand’ in the last update of TimeXtender (6024.1). I will definitely use this for hourly reloads. However, in some cases, especially when working on larger tables in the MDW, it would be convenient to have the option in the execution setup to NOT reload on demand. In that case, when for example deploying and executing a small change (e.g. change of a fieldname), this will not result in a full load all the way from the source.