Okay that’s what i wanted to know. I’m just surprised it works on the 8852au but then again not really. 
Edit: The chip doesn’t know any better … but then again sometimes it does! 
Man, you dont wanne know the “words” coming out of my mouth over the last days while trying to make it function 
I can just imagine. 
Edit: So you still have the issue with the other WiFi with Bluetooth?
And now, after blacklisting the buildin wlan, i know also the channels and frequencies and will try to tweek the AX-part in the conf
43: USB 00.0: 0282 WLAN controller
[Created at usb.122]
Unique ID: FKGF.V+b7PR3LSQA
Parent ID: pBe4.xYNhIwdOaa6
SysFS ID: /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0
SysFS BusID: 2-1:1.0
Hardware Class: network
Model: "ASUSTek 802.11ax WLAN Adapter"
Hotplug: USB
Vendor: usb 0x0b05 "ASUSTek Computer, Inc."
Device: usb 0x1997 "802.11ax WLAN Adapter"
Serial ID: "00e04c000001"
Driver: "rtl8852au"
Driver Modules: "8852au"
Device File: wlan1
Features: WLAN
HW Address: 10:7c:61:33:f2:14
Permanent HW Address: 10:7c:61:33:f2:14
Link detected: yes
WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140
WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.5 5.52 5.54 5.56 5.58 5.6 5.62 5.64 5.66 5.68 5.7
WLAN bitrates: 1 2 5.5 11
WLAN encryption modes: TKIP CCMP
WLAN authentication modes: open wpa-psk wpa-eap
Module Alias: "usb:v0B05p1997d0000dc00dsc00dp00icFFiscFFipFFin00"
Driver Info #0:
Driver Status: 8852au is active
Driver Activation Cmd: "modprobe 8852au"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #49 (Hub)
yes 
I read that the kernel-modules can be given a sequence in what they are loaded and i will try to let load the rtw_8821ce as latest and see if then the ASUS, cause installed before, is not compromised by the later insalled rtw_8821ce. But have to read some pages for that.
yes, i blacklisted it. But cant install it later with terminal “sudo modprobe” cause blacklist means also there will be no files in lib for that
[as@kiste ~]$ sudo modprobe rtw_8821ce
[sudo] Passwort für as:
modprobe: FATAL: Module rtw_8821ce not found in directory /lib/modules/6.12.7-arch1-1
[as@kiste ~]$
So blacklist is not the solution and i will try not to blacklist it, but give it the last module-loading-number.
Not sure how you do that? 
Well, not sure. Maybe like in /lib/kernel/system.d. But me think it has changed a lot with going from SysVinit to now systemd. But hey! There is also good news!
I unblacklisted the rtw_8821ce and rebooted for to see if still interfere with the ASUS and then guess what? I suddenly had TWO connections with the same name to the Fritzbox. Parallel. 
And in the Fritzbox both were shown under WLan-connections. Maybe that was the reason that there were problems with the ASUS. I deleted the rtw_8821ce WLan-connection, reactivated bluetooth with
sudo systemctl enable bluetooth.service
then did a reboot and now all is fine 
So now only finetuning of the ASUS ax-part is left. If finished i will post. But for know i need a pause 
Why did HP put RTL8821CE in a laptop with 11th generation i5 CPU? 
I would expect something better or newer.
@ricklinux 0b05 1997 is indeed RTL8832AU, not RTL8832BU.
Cause it is HP? 
meanwhile me think the RTL8821CE is not worth a penny
Well i have an HP with that chip and it works fine. 
There are several versions of RTL8821CE. Maybe yours is the one the rtw88 team tested more. I don’t think they had access to all of them.
You can check which one you have:
grep RFE /sys/kernel/debug/ieee80211/phy0/rtw88/coex_info