It seems most banks love to tie their services to a smartphone and employ activation procedures that make users jump through hoops and have no way to transfer it to another phone without contacting the bank. 10 years ago, you could have a certificate on a computer and things were simple(r). Now certificate is replaced by a smartphone...
I somehow got both apps working in the end, now I don't even know if replacing Magisk was necessary because in the end, I had to force basic attestation through MagiskHide Props Config for the new app to work surely. Not sure why the new app launched at first without it. I noticed first app doesn't lunch at all when completely removing Magisk.
if I knew to look into MagiskHide Props Config first, which I had installed, just didn't actually use (figured it might come in handy some day)...probably needlessly restored partitions few times because I assumed the process broke something permanently...
In the past, I was restoring partitions on the phone using Linux on desktop PC and used a chain employing netcat and ADB's TCP port functionality. Didn't know I could just use adb push, pulling partition from the phone works when referring to partition's symbolic link, but not the other way around. Pushing works as long as you refer to partition's path directly, eg. /dev/block/mmcblk0p24 for data partition on my model. Path to symbolic link is longer and descriptive, you know exactly which partition you're targeting. But when you know the numbers, referring to them directly shouldn't bring any surprises.
Flash memory is still holding, it's just that adb pushing on Windows was slow on my PC. Seems to be noticeably more performant on same machine on Linux. I'd have to try again to be absolutely certain about exact numbers, but in best scenario, it's something like 3 MB/s on Windows and 6 MB/s on Linux. No idea how apart ADB versions were, my Linux has whatever version came in the Ubuntu's repos in 2020 if I'm not mistaken.
One interesting difference that I noticed, that ADB on Linux I have always does "push install" for app installations via adb install command. The old ADB on Windows I have does "streamed install". But brand new ADB downloaded recently straight from https://developer.android.com/tools/releases/platform-tools on another computer running Windows also does "push install". I think "push install" sends the whole APK file to temporary folder before install while "streamed install" doesn't.