A possible solution approach has been been explained in the topic you've linked.
No, as explained at length in the thread you've linked:
Pi-hole does not use dnsmasq, but brings its own pihole-FTL binary, (which happens to be a tailored fork of dnsmasq, but that isn't relevant here).
pihole-FTL is configured via configuration files from /etc/dnsmasq.d/ and /etc/pihole/.
NetworkManager is able to start dnsmasq processes as required.
NM configures them via configuration files from /etc/NetworkManager/dnsmasq-shared.d (for its hotspot service) and /etc/NetworkManager/dnsmasq.d/ (for its DNS service).
While configuration files are cleanly separated, still both pihole-FTL and NetworkManager's dnsmasq would try to claim port 53 (DNS), port 67 (DHCP) and port 547 (DHCPv6) at startup - if they would be configured to do so.
So for NM's dnsmasq DHCP service and pihole-FTL's DNS service to coexist, you 'd have to make sure that neither one uses the ports of the other.
If you want Pi-hole to handle DNS, the way to avoid this is described and explained in yubiuser's first reply to that post you've linked:
To disable specifically the hotspot's DNS service, you'd have to create /etc/NetworkManager/dnsmasq-shared.d/disable-dns.conf with a contents of port=0. Configuration changes would require a restart of the services to be affected.
The topic you've linked also details additional measures to concert coexistence as provided by MichaIng, e.g.: