See "bro" | "god" | "nerd" or whatever people call you. IMHO you've no clue what you're talking about and again you don't respect the rules:
Bug reports without a suitable log will often be ignored - no debug log, no issue - or at best will take much longer to be investigated.
But since I'm in mood to tell you how this build works... let's enlighten you.
It's totally normal to use echo 1 > /sys/module/bluetooth/parameters/disable_ertm for other Linux distros too. Gamepad - ArchWiki
Also the Xbox controller has a long history of problems:
Xbox One S Controller, Fix for Select not working via Bluetooth · Issue #2023 · RetroPie/RetroPie-Setup · GitHub
Fix Xbox One S Bluetooth Select Button by daviderickson · Pull Request #4 · RetroPie/SDL-mirror · GitHub
Xbox One Controller - Bluetooth
So maybe think twice before you buy a controller.
You're refering to your Xbox One controller and the fact that the left analog stick works as a mouse in Kodi. Well yeah so if in your opinion the input mapping in Kodi is wrong... where should you file this bug? Probably in a Remix build that's focused on Retroarch & Emulationstation. Makes sense. Totally.
Retroarch uses udev as default to detect your controller and load a matching config file. These config files are provided by retroarch-joypad-autoconfig/udev at master · libretro/retroarch-joypad-autoconfig · GitHub and have nothing to do with Kodi. All libretro-cores use this mapping and are not affected by ES or Kodi.
Emulationstation relies on SDL2 and uses this file to detect your controller sdl_gamecontrollerdb.h and tries to find a matching mapping in es_input.cfg also this mapping is only used for ES menu navigation. All emulators based on SDL2 use the same gamecontrollerdb or gamecontrollerdb.txt to detect controllers and either automap them or allow you to map inputs. Well beside Amiberry that uses SDL2 to detect your controller and is RA mapping compatible but that's another story.
So we conclude one frontend mapping does not impact any other frontends and you have to set up your controller properly if you run into problems.
About your tty problem... well it's interesting how you don't understand that escalades build is based on LE 8.2 and mine is based on LE 9.0. And when you're talking about "official" then you're referring to what? This one libreelec-generic.x86_64-8.2.5.img.gz or this libreelec-generic.x86_64-8.90.006.img.gz ?
Since tty is missing here LibreELEC.tv/mkimage at master · LibreELEC/LibreELEC.tv · GitHub and here LibreELEC.tv/installer at 3230a0838bb43648a935b8a0f14b0eebd1d8cc26 · LibreELEC/LibreELEC.tv · GitHub so there is no tty on official LE alpha builds. If you really need one follow this guide Raspberry Pi Config.txt [LibreELEC.wiki] to unlock your flash partition and add tty to the line APPEND boot=... in /flash/syslinux.cfg
Enabling tty by default could be a major security risk if you use LE in a public environment so a pretty good reason to disable it.