An educated guess is .. you didn't set whitelist entries so everything is running at 60Hz instead of 25/50 or 29.97/59.94.
In Kodi video settings.
I'm not sure it's the reason, but all the Netflix developers are German 
Add-on suggestions are best made via the respective add-on support thread in the Kodi forums.
We'll add that to the list of things CE don't understand then. It's a lengthy list.
Long story short .. there's nothing in the logs. For the sake of experimenting please configure things then stop Kodi with "systemctl stop kodi" and then reboot. Is the calibration preserved? .. this should isolate whether it's the multi-year recurring issue of the OS hard-terminating Kodi (because it's taken far too long to shut-down) which can corrupt guisettings.xml and results in a new file on restart. Also useful to know .. do other settings get lost too?
LE supports update from .tar file and .img.gz so it's not a problem.
As a rule LE (the OS) and Kodi are a simple update. The challenge has always been user-install add-ons. The more junk that's installed the greater the likelihood of something having issues. Make a backup and move it off-box and you can always recover things.
We don't support auto-restore from backup on first boot (and have no plans to add it) but in LE 9.0 the first selection on the first-run wizard is a language chooser .. which might help.
Current efforts are not in vain, and while I can't go into details, I don't have concerns about S905X2/D2 support.
I'm not sure whether ARM's open-source group have been given the internal approval to submit code to Panfrost yet, but the request has been made and they're keen to start. Meanwhile a couple of ARM engineers are engaged with the Panfrost devs, testing code, and generally finding other ways to be useful. We (LE) are partly responsible for some of the those connections being made
Kodi uses libaacs to read BR media and libaacs will not function unless there's a KEYDB.cfg file present with appropriate content for the disc that you are trying to play. I have no personal knowledge on makemkv so I can't comment on how you'd make that work.
The alternative is a huge number of spam bot posts per-day which is repetitive and demoralising work for the forum staff who already give up a large amount of their personal time to help the project. We value making their forum lives easier above a little wordplay inconvenience for users. Sorry but it's not going to change.
Lima submitted its kernel driver today. It's not the first submission but this time around it has a fairly distinguished list of "Signed-off-by" signatures on-board so I'm hopeful it goes into the 5.1 merge list and there's a date that I can drop one of the larger patch-sets. Panfrost also merged initial mesa stub support which will make mesa packaging easier from 19.1 onwards. All over the codebase we're starting to see lots of the jigsaw pieces slot into place although community development is often a frustratingly slow process. I'm confident that in the future we'll be able to release a single Amlogic image that supports GXBB + GXL + GXM devices, though that's a long-term goal (not in in this half of the year at least).
05:21:38.302 T:1790935920 DEBUG: CurlFile::Open(0x6abf7ab8) http://mirrors.kodi.tv/addons/leia/addons.xml.gz
05:21:38.555 T:1790935920 DEBUG: CCurlFile::Open - effective URL: <http://103.1.138.206/mirrors.kodi.tv/addons/leia/addons.xml.gz>
05:21:38.626 T:1790935920 ERROR: CRepository: http://mirrors.kodi.tv/addons/leia/addons.xml.gz index has wrong digest aaec368750d01ade4908bc50e2c5bf37020fbae588d1d083f668ee2c33b59f03, expected: ������addons.xml����G�'��鯈�k��uW�y�1����F�Y���EUFWeWVf)�T?�
�Ѐv@ !��oh�fWp�?5�{�k��E,4b��_��Gdfe��Kodi uses geographic mirrors provided by volunteer third-parties to host add-ons. It looks like the one you're accessing is out of sync so the checksum doesn't match and Kodi cannot load the repo files. The problem should correct itself with time; either because a future request will be redirected to a different mirror (if there are multiple mirrors in your part of the world) or because the mirror will resync and have the right files again. If there's a single mirror that you consistently prefer (are redirected to) and it's wrong .. there's not much you can do. Plan B is to find a Kodi mirror and download the zip file for the addon and install it manually, although YouTube has external dependencies and you'll need all those too.
Log shows the ntp service works, but the mount attempt is some time before the clock is updated.
Create /storage/.config/autostart.sh and add the command "date -s "06 FEB 2019 11:10:00" (make it to something close to current) and reboot. I'm wondering if negating the clock drift solves anything? Is there any difference when using the default (pool.ntp.org) servers?
Downgrading the connection to SMB1 shouldn't be required (as it mounts fine). It's just a workaround for some other issue. Do a clean boot, let the mount fail, and then run "journalctl -b 0 --no-pager | paste" and share the URL here.
I have a hunch the issue is ntp related.
Read post #24 again. Follow the comments in the files.