l/also fine as follow-up: Wdyt about making this a utility function? We have very similar logic in our event processing pipeline

as well as in Node ANR (though admittedly I don't care much about the bundle size there)

might save some bytes and it might help us get rid of the complexity eslint comment (though again, low prio obviously)

also can we rename this to e.g. getMergedScopeData() or something like this, was not clear to me from the function name that this would consider isolation scope etc :)