If you scraped media into the library from smb://nas/share/files, this is the path stored in the library. If the NAS is now accessed using smb://192.168.1.10/share/files the path is different and Kodi treats this like new files.
First, try this to see if it restores name resolution:
echo "192.168.1.10 servername servername.local" >> /storage/.config/hosts.conf
rebootOr experiment with path substition https://kodi.wiki/view/Path_substitution
Is there not source code for the u-boot firmware?
Amlogic sources exist but 99.999% of manufacturers "tweak" the sources to work with the components of a specific box (including the remote codes needed for that model) and if the RAM chip timing/specs are changed (always) this makes the u-boot binaries unique to a specific box. Unless you know what changes to make, the compiled u-boot binaries won't boot the box. Universal IR remotes are always easier.
The AMLGX image works with S905W boxes, but you will have to see if the p281 device-tree boots (or Tanix TX3). These super-cheap boxes often have WiFi chips like SSV6501 that have no upstream drivers so the box will probably be Ethernet only.
Check the MAC address (visible in Kodi settings). Does it change on each reboot?
If yes, this is the reason the settings aren't persistent. ConnMan stores service details in a format that includes the MAC address, so on reboot when it changes there's no matching existing service and you need to repeat the process.
The cause is probably something specific to the board, but i'm not personally that well versed in Rockchip things.
I've started to chase this through Team Kodi contacts. We have direct chat access to several people, one of whom has been copied into the ticket. These things take time and (us) trying to escalate them is often counterproductive.
I've recently seen media that only displays a "stop" button in the OSD and the underlying issue was the container (mkv) reporting no duration and thus Kodi has no way to calculate progress. Kodi logs showed this:
Duration: N/A, start: -0.005000, bitrate: N/ANo guarantees your media is the same, but maybe..
Two suggestions for organising things:
Have a look at the "node editor" add-on in the Kodi repo. Nodes are things like "recently added" and "genres" that appear in the GUI, so they combine a node name (can be anything) with saved searches (inclusions and exclusions) and sorting to leverage media metadata in the library DB. I've no idea how that function might be influenced with Emby as the underlying back-end, but it's worth a look.
Kodi Omega also gained a new "versions" capability for movies, allowing e.g. the standard movie, the directors cut, the 3D version, the fan remix, etc. to be stored under a common movie name. Race Weekends are not movies, but some creative abuse of .nfo files and the local file scraper could probably bastardise things into showing a movie name (Race Weekend) with different versions of the movie (Practice, Qualifying, Race, etc.).
There’s never any harm sharing your achievements either.
If you do fix something, send the fixes upstream for the benefit of all. Best case the fix gets merged. Worst case it might be critiqued (coached) for some improvement or borrowed/reworked by upstream devs or another contributor.
`I'd suggest an update to a current LE12 nightly as there are newer versions of drivers and BlueZ included, and rework to the settings add-on to change how the list of devices works that might improve usability. However the main reason is LE12 has been the focus of development for the last year and there are no futher LE11 updates planned.
I guess I was potentially trying to emphasise the issue in order for it to be considered in that rework.
"Versions" is the gift that keeps on giving .. the initial merge looked simple but then the 101x unconsidered corner-cases where it had unexpected impact started to show and it's been a complete pain in the rear to fix things; most of the original code has now been reverted and reworked to avoid or better resolve problems. If you report stuff in Kodi forums please be mindful that the devs who read of more issues will be "delighted" to know there's more 
The IR wake codes are hard-coded (compiled) into the u-boot (boot) firmware. If your remote does not send the right code and/or cannot be reprogrammed to send the right code, there is nothing we can do. The boot firmware would need to be recompiled with new codes, and 99% of Amlogic set-top box devices have no source code for the boot firmware.
It's not impossible to get these drivers working, but it requires someone with a huge amount of time and far greater coding skills than myself, and the final result will never be accepted upstream due to issues with code provenance. In reality the generation of GXBB/GXL/GXM boxes that have tuners inside will have died and gone to landfill long before someone volunteers to do the work.
I'd rephrase "We don't answer CE questions here" as "better to ask CE questions to their devs in their forum.."
This image has "CONFIG_MEDIA_TUNER_M88RS6000T" enabled, which is the upstream driver:
https://chewitt.libreelec.tv/testing/LibreELEC-AMLGX.aarch64-11.80.0.tar
NB: CONFIG_DVB_M88RS6060 only exists in the vendor kernel.
Test and report back on whether it works. If it does I'm happy to add it to the default image.
Sorry but I'm not sure what you're trying to tell me or ask me? 
Versions is a new feature that's had a challenging introduction (lots of rework needed since initial merge) so the best place to ask for help with it is the Kodi forum; as that's where the developers who've done (and are still doing) that rework, hang out.
The 7/10 quote comes from myself and I generally see HEVC being quite good with 23.976 movie media and less well behaved with TV content that's mostly 25/29.97 format, i.e. it's all about the original source and how I ripped stuff .. but my experience isn't going to be the same as everyone else's. I did manage to guess a fix for a VP9 playback issue recently, but that's not relevant for C2 users (as S905 doesn't support VP9) and otherwise there's no real-world changes coming in LE12. There has been some commercial work funded by LibreComputer on the hardware decode drivers in the last year, but that work hasn't resulted in something meaningful/testable yet, and right now the effort is stalled pending availability of more funds and some deep technical info from Amlogic.
Best place to look/ask is in the Kodi forums support thread for the skin. Last I looked it hadn't been updated in a while and needed some work for compatibility with Kodi Omega. It's not uncommon for skins to remain outdated until after the Kodi RC releases start or the final release takes place; then people appear, send a few needed changes, then crawl back under whatever rock they've been hiding under. The folks who've maintained it in the past haven't been active/seen for a while though.. so no guarantees.
https://libreelec.tv/ .. click on any LE11 release
I'd suggest an RPi5 with a flirc case. You don't need the 4K capabilities but they exist if/when that changes. It's a fast and simple device and RPi is the gold-standard for LE software support. If you're on a budget an RPi4 is largely the same and will be cheaper, though a little slower (but not slow).
