The problem is the definition of "realistic enough".
The protocols you mentioned are Application-level protocols, and you are modeling them as "plain" TCP connections with an average bitrate. This might be ok-ish for a simple simulation, but you're missing all the protocol details, so it's hard to say if the simplification is too much or not.
As an example MQTT is indeed using TCP, but it's a Pub/Sub protocol, and modeling it as a "plain" TCP connection omits all the ACKs, periodic messages, unsolicited messages between the broker and the Subscribers, and so on.
Is this a critical point? Depends on the level of fidelity you need.
About the lack of packet drops, all your connections are P2P.
If the datarate of the sources do not exceed the link capacity you'll never see any packet drop.
I didn't check the numbers, but it's simple enough to do the math.
It would have been different with wireless links, because packets could be dropped by channel errors, but on P2P or CSMA links the only drops are due to:
- Error models on the links (you didn't add any), or
- Link capacity exceeded (and finite buffers on the NetDevices).
but to see the link capacity exceeded drops you'd need (probably) bursty traffic (not very SCADA-ish tho).
Suggestion: before tweaking your simulation I'd work a bit on the system model, and the definition of what you're trying to optimize.