Yes you could approach it from that side as well, where you have 1 single function that sits outside all of the replicated items, and along with the regular info you’d like to send it, like rgb values etc, you’d also send the number or name of the item you want operated on, and it would create a path to the item before running its set of actions.
Really depends how you’re comfortable and how you’ll be transmuting it down the line I believe. This run way is pretty straight forward for perhaps this one.
For future ones, you might actually want to check out the new python extensions in builds 21000+. Then you could do what you mentioned where it would be op(‘example’).updateStats(r,g,b,etc). I’m just scratching the surface with them, and they’re a little bit buggy since it’s an experimental build, so if you’re doing this for a job, probably stick with the op.run method for now, otherwise would be good to experiment with the extensions.