See the documentation listed under each warning:
https://docs.pi-hole.net/ftldns/dnsmasq_warn/
Clients connecting to WiFi is separate from any Pi-hole activity. That is a transaction between the client and the router.
That's not what the clients are seeing:
*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
Scanning all your interfaces for DHCP servers
Timeout: 10 seconds
* Received 300 bytes from eth0:192.168.50.1
Offered IP address: 192.168.50.127
Server IP address: 192.168.50.1
Relay-agent IP address: N/A
BOOTP server: (empty)
BOOTP file: (empty)
DHCP options:
Message type: DHCPOFFER (2)
server-identifier: 192.168.50.1
lease-time: 86400 ( 1d )
renewal-time: 43200 ( 12h )
rebinding-time: 75600 ( 21h )
netmask: 255.255.255.0
broadcast: 192.168.50.255
dns-server: 192.168.50.1
router: 192.168.50.1
--- end of options ---
DHCP packets received on interface eth0: 1
DHCP packets received on interface lo: 0
DHCP packets received on interface wlan0: 0
There is an active eth0 interface. The warning may have been generated on Pi-hole startup if the ethernet interface had not yet become active:
eth0 (192.168.50.126)
Your gravity list is empty:
*** [ DIAGNOSING ]: Info table
property value
-------------------- ----------------------------------------
version 15
updated 1665907501
gravity_count 0
Last gravity run finished at: Sun Oct 16 03:05:01 CDT 2022
You have no subscribed adlists:
*** [ DIAGNOSING ]: Adlists
*** [ DIAGNOSING ]: contents of /etc/pihole
Restore at least one adlist, then rebuild gravity.