Hello, is it possible to use with this version Netflix, Amazon add-ons via inputstream.adaptive or I need Libreelec 9.0 test version?
It will work, but inputstream support for those services is currently a fluid moving target and most community image creators aren't updating the add-on as frequently as the upstream sources are being ad-hoc changed. You will need to track/update the add-on frequently.
modprobe rtl8192cu
echo "7392 b822" | tee /sys/bus/usb/drivers/rtl8192cu/new_id^ if you do that, it works? - if yes we can get the device ID's added to the driver.
It should be persistent by default and there is nothing in the OS that allows you to configure (disable) persistence. It sounds like a bad/corrupted (or worst case, fake) SD card.
LE is not a NAS distro and you don't appear to be using LE clients. And you're expecting things to be the same after inserting a 100-BaseT switch between server and wireless connected clients and playing media that's twice the size as before (albeit still not that large). TL/DR; I'm not convinced this is an "LE" use-case that we'd have any responsibility to support. Use FreeNAS or unRAID.
We have specific sub-forums for community created images where the authors support their stuff. Everything else goes in a small number of general categories; because this results in more eyeballs seeing threads and we see much better audience participation. We know from OE era experience that creating lots of forum micro-categories results in few people seeing posts and a higher support burden on the mods/staff.
Install LE to the internal eMMC and it will run faster. Install LE to an SD card and it will run slower. You will have the same experience on pretty much all hardware - it's nothing S912 or Amlogic specific. NB: most far-east box manufacturers procure the cheapest components they can find and "the box boots Android" is the only performance test they do. If you want something faster it's time to $pend on a NUC or similar.
I'm not aware of anyone working on LE support for HiSilicon SoC's or anyone in our extended developer team or surrounding ecosystem having any contact with HiSilicon staff. Changes coming in Kodi v18 will make adding support considerably easier for any SoC vendor with a well maintained and current mainline kernel and V4L2 drivers; but that description mostly excludes far-east manufacturers with a "hack it to boot Android" mentality. So who knows..
If someone submits the add-on code to our repo along with a pledge to maintain it over time we're happy to build and publish - otherwise I'd see it as an über-niche requirement; AFAIK you're the first person to ask for zabbix in the ~6 years I've been hanging around the LE/OE team.
zabbix-agent might be an easier option. Probably not as efficient in terms of "small light agent" if it requires a nice big fat OS image to run the agent, but functionally it'll do the job.
Can you share a media sample?
also provide kernel journal log..
I have no personal experience of the WP1 but there's a reasonable population of daily-active installs and the rate of reported issues here is fairly low so I assume there are no major issues. Amlogic support in Kodi isn't perfect, but Krypton exorcised a smorgåsbord of hacks that caused problems in older Jarvis and OE era releases. For any meaningful "playback" support you'll need to start by sharing some Kodi debug logs that demonstrate your problem, then maybe media samples if we need to replicate something. As an aside; WP1 is not a fast box so running from the internal NAND would be advantageous over using an SD card.
user changes should go into /storage/.kodi/.smb/user.conf so that GUI driven changes don't remove them.
It's not really been discussed. Largely because most decisions depend on the next 3-4 months of Kodi Leia development.
Back-up the old config and clean install the box. I'm never surprised when spring cleaning all the old cruft out of an install solves problems.
Raspberry Pi 3 is always a safe bet.
There are no specific plans at this moment. Kwiboo (and others) started Rockchip work on the Tinkerboard, but that only has HDMI 1.4 and broken CEC so they picked-up a better spec no-name device and then moved on again recently to poke sticks at the ROCK64. The main objective is RK3328 support in the OS (which leads to good Kodi/mpv support) and not specifically creating LE images for the ROCK64 or any other device. There are fun decisions to make about RK3328 and Amlogic in the mid-term future 
You can run Chrome in a Docker container, but that's the only option. It won't run natively because Chrome is released in pre-compiled binary packages that are not compatible with our OS; hence we compile our Chromium add-on from sources.
No, because it has a Rockchip 3229 chipset.