Sadly, I have to report that my report as a separate issue was probably erroneous and downgrading the firmware package to 20200916-1.1 did fix the issue for me as well.