In host mode, the container would directly share the host's network, i.e. it would not have created additional IPs, but have had shared access to your 192.168.2.28.
Your docker inspect results show that your Docker host network is sparsely configured:
"Networks": {
"host": {
"Aliases": null,
"DNSNames": null,
"DriverOpts": null,
"EndpointID": "a1964731ec04ac49cbc2a95ef1670878363371639fbf1ec4068901950c0ffec5",
"Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"IPAMConfig": {},
"IPAddress": "",
"IPPrefixLen": 0,
"IPv6Gateway": "",
"Links": null,
"MacAddress": "",
"NetworkID": "d84939c79d2832ea558248312d3507ed5b1220ab710adbb52cbb06b9fac8c1d9"
}
It's basically missing everything that would make it operational.
For a long time, Docker didn't support host network mode on Windows (as the docker daemon itself runs in a VM on Windows, i.e. it really can't share the host's network interfaces with its containers).
I think Docker started introducing host mode for its beta releases late 2024, but I wouldn't know whether that has GAed by now, nor how to enable it.
It would be easiest if you would run your Pi-hole container with Docker's default bridge network.