[Xiaomi Redmi 4X ROMs, Kernels, Recoveries, & Other] SebiderSushi:
Attached find a TWRP backup of Persist, but do read all cautionary remarks before use

I tried boiling down the contents of my persist partition to a bare & hopefully non-personal minimum.

I did definitely find my bluetooth MAC Address within the file "bluetooth/.bt_nv.bin" in the persist partition, so i did't want to share an unfiltered backup of this stuff.

What i did was to guess which files are probably unimportant and delete those. I also compared the persist backups from two Redmi 4X devices. Out of the files within the attached TWRP backup, only "sensors/sns.reg" was different between the two devices. I suspect that this file contains device specific sensor calibration data, so beware that restoring a foreign file for this purpose might lessen the precision of your device sensors.

I did test the attached TWRP backup. After restoring it, i can boot and sensors & Wi-Fi appear to work normally. BEWARE THAT BOOTING WITH THIS BACKUP DID CHANGE MY BLUETOOTH MAC ADDRESS which should never happen.

MY RECOMMENDATION

DO NOT just restore this TWRP backup,

even though you can. You might restore the backup to test if it fixes sensors in your case, but as TWRP replaces all contents of the Persist partition with the files from the backup, i strongly advise against running your device with just this backup from now on.

What i recommend is that you take some time, boot TWRP and `adb shell` into your phone from a PC so that you can comfortly debug this problem on a proper PC keyboard and not on your touchscreen on your Phone and in TWRP. This also gives you the option to open as many windows as you need in parallel.

Technically you can also do the next steps completely on your PC, but as you mentioned that you had problems using simg2img i suspect that you are using a Windows OS on your PC and i am not familiar with how to do the following on a Windows PC. The tools i'd use are available under Linux/Unix environments which is why it also works right on your phone.

Once that is set up and you have a shell running on your phone, you should take the file "persist.ext4.win" and extract it like so

mkdir -p /data/media/0/persist_mangled/ &&
cd /data/media/0/persist_mangled/ &&
tar xvf /sdcard/persist.ext4.win

Then, restore your original backup of Persist and make sure that "Persist" is mounted on the "Mount" screen available on the TWRP main screen.

After that, you can start to check for differences between the files in "/data/media/0/persist_mangled/" and "/persist/". Useful commands for this can be:

ls -la [<directory (optional)>]
md5sum <file(s)>
diff
cmp

What to look out for:

Permissions: Maybe everything is there and it is just a matter of faulty permissions

sns.reg: SInce you are having trouble with sensors, checking out sns.reg and possibly copying over just this file from my attached TWRP backup will fix your issues.

I hope this helps you enough and that you can even use & apply this information to begin with.

If you are absolutely overwhelmed by all of this, you could also send me (privately!) your TWRP backup of your faulty Persist partition and i might as well take a look at it to find out what might be wrong with it. That is, of course, if you trust me with it.

My last advice will be a lot more obvious though and it's that once you do get it working you should make TWRP backups of all the special partitions (EFS, Persist, ...) that you can in order to avoid things like this in the future :)