We could do however, it just moves the problem somewhere else in the future and we’ll end up playing whack-a-mole fixing each individual issue one at a time and we’d end up in the same situation of having all bundle assets call UpdateAssetBundleData but we’d be doing it the long way around.
If there was some kind of validation that we could run during pre-submit tests that would catch this issue then we could potentially revert this change.