The issue reported uses the compatibility pipeline that's built into SBP. We've fixed this issue in regular SBP 1.21.5, but the compatibility pipeline is a completely separate code path that would require engine changes. If you're not using regular SBP, or SBP through Addressables, opting for the native asset bundle build pipeline might be a better option for the time being.