I also like that.
Btw Onomondo claim approx. 40uA savings
For eDRX, which then comes anyway with higher energy consumption, when the receiver is enabled more frequently. In my experience, a common SIM in eDRX takes about 25µA (measured at the battery), I guess the 40µA are at 1.8V. Anyway, a SoftSIM, if it gets available also for small projects, would be great and would obsolete the eSIM.
With my last experience (nRF Connect for Desktop / Programmer), the point with the Tag Connect is, that it’s usually only connected for a short time. But that programmer tool needs to connect it when starting the app. A mini SWD would make that easier.
In my experience, such a fuel gauge (e.g. Thingy:91) has some advantages over the battery voltage, especially the values have less noise. BUT it is also fixes somehow the battery type. If you want to run e.g. a low-self-discarge NiMh, then it may not be possible to adapt the setting for that. So my favorite would be to connect the nRF9160 direct to the battery and use AT%XVBAT. The downside would be, that the max. battery voltage will be only 5.5V instead of the 6.5V. To build a soft gauge with that requires that you record some usage voltage charts for your setup (I’m used to do that with enable GPS and send the battery voltage to the cloud every 10 mim). That chart will then be the base for a linear approximation in segments. That’s also the idea for the current approach with the ADC for the battery.
(By the way, the current documentation mention 3v as minimum. In my experience, the minimum for that buck is 3.3V from the battery.)