Hello there, and wanted to say initially, that sounds like a pretty tough time and detail to work through and sorry you are having to deal with it.
TLDR;
No, you might have enough to setup a listener, but it would appear you do not have enough to run the network path across that listener and use the internet at the same time.
The Long;
The response direction you are seeking while challenging, and possibly not going to get you what you want, can be had but likely with more hardware and some fairly complex configuration.
In short, if you have those components, and are not sure if you can do it - you will likely have a pretty step climb to be able to inspect your traffic. Not impossible, just a step climb.
About what you thoughts on being targeted, for someone to pull off DNS/ARP spoofing, they would have to have local access to your network OR devices. The would either need to control your DNS (either by changing settings on your hosts, or some level of reconfig/rootkit that is modifying how your actual router works) or have a device that is on your network messing up your router. These are not easy things to do, at all. In most any problem, the simplest solution/cause, is most likely. To this end, there is a good chance a buggy device/setting is causing the issue or someone browsing/using some ‘not legit’ software (hacked game/ISO-mounting software w/keygens or something) and you actually have a virus on your network.
In this some cheap/ISP routers are full of CVEs (vulnerabilities) and easily hack-able from ‘outside’ of the router. It is usually nation-states/APTs doing this, and they have scripts that crawl the internet trying to ‘make more bots’ for their bot army. Usually these guys do not ‘break the bots’ user neighbor’ as that usually means the user (in this case, you) figures out something is up and eventually kills their bot (replaces hardware/router etc.), but, not all script kiddies act alike. Simply getting a new/upgraded router w/proper hardening on its settings (care on the port forwarding and the like) can do wonders. Also, getting some proper Anti-Virus can be very wise.
That all said, I did a quick search on how to setup an IDS at home because there are so many elements in the mix, where you are watching from (inspecting packets from), what you are watching (http/https/dns/etc.), and the rules you use to do the detection. I would recommend you attempt to explain your intent to inspect your network and understand when encryption might prevent you from seeing something unknown, before you have to realize that most of the traffic on a network is encrypted and likely going to prevent you easily finding a culprit if one exists in the first place.
Yes it is Snort, but they work about the same way (Suricata vs Snort) and the logic about where you put it and how it listens is exactly the same
This video discusses using OPNSense (or your could deploy a PfSense) as your router so you get your IDS at the main point of your network. If your ISP lets you BYOR (Bring Your Own Router) then you are in luck, this is probably the easiest way to get Suricata/IDS at a place that can have an impact.
You can build your own Suricata, but again, the first hurdle is to be able to watch a network path that matters, and generally for a home network that is all the devices and a simple laptop will not have the network adapters to pull this off.