PiHole stopped working after DietPi OS update interrupted

Could you try above one again, maybe a typo, bc if it doesnt output anything, below one also shouldnt right?

Which would mean those files are gone now somehow (EDIT: or all directives are hashed out/commented).
Below is an example of a skeleton config:

$ sudo rgrep -v '^ *\(#\|$\)' /etc/network/interfaces*
/etc/network/interfaces:source-directory /etc/network/interfaces.d

Or below on another Linux box:

$ sudo rgrep -v '^ *\(#\|$\)' /etc/network/interfaces*
/etc/network/interfaces:auto lo
/etc/network/interfaces:iface lo inet loopback
/etc/network/interfaces:auto eth0
/etc/network/interfaces:iface eth0 inet dhcp

Above output is confusing me bc its mentioning a wireless interface wlp170s0 and not eth0.
It also seems to be still connected via Wifi.
What does below output (it redacts the MAC's)?

ip -br l | awk '{print $1,$2,$4}' | column -t

dhcpcd works like so, if you dont configure any IP details for particular interfaces, like in your case from above output, it will try to automatically acquire IP details via DHCP for all detected interfaces.

You either have to configure manual static IP details via dhcpcd.conf,
or you have to purge/uninstall dhcpcd from your system and configure static IP details in the /etc/network/interfaces file (or files in the .d folder if configured correctly) so ifupdown can configure IP details instead of dhcpcd:

$ systemctl is-enabled networking.service
enabled
$ systemctl cat networking.service
[..]
Description=Raise network interfaces
[..]
ExecStart=/sbin/ifup -a --read-environment
$ man ifup
[..]
DESCRIPTION
       The  ifup and ifdown commands may be used to configure (or, respec‐
       tively, deconfigure) network interfaces based on interface  defini‐
       tions  in the file /etc/network/interfaces.

EDIT: below a dhcpcd example:

You have to decide which one you want to use?