Thanks @datajoely ! I think that lists all the nodes without actually running them, but maybe we could adapt it to replace certain tagged nodes' input/output. Though I don't know what the 1. most "kedro-friendly" way 2. easiest way would be, since the method in the issue I linked would require us to perform changes in two separate catalogs if anything changes, but the custom runner requires more development, and additional testing