Hello and thanks for the reports!
We’re aware and planning some changes to address this in the upcoming 2.0.3 patch.