Can Microsoft make it anymore confusing? We now have 18362.327, 18363.327, 18362.10014, and 18362.10015.
kb4517245 is a feature state enablement (like mach2.exe) i don't know if there is anything physical i could detect it see how WinPE images didn't got bumped to 18363, even with kb4517245 that's how DU treated, merely extracted as-is fixing...
The 1909 enablement RP package doesn't bump the build to 18363 when already on the SLOW ring 10015 19H2 (atm) but on 10014 it will enable some features like the new explorer search box (found by @whatever127) on 10015 it doesn't.