There isn't a big difference in "secure" for the most part. If the data is an encrypted volume, then it's encrypted on both. The problem is more that when you try to erase data, SSD's do not erase data as reliable as an HDD does.
This is about the wear-leveling mechanism in SSD disks. HDD does not have this issue. So, an external HDD is fine, but an external SSD is not recommended.
Now, the absolute majority of VeraCrypt hidden volume users will never have their storage sent to forensic labs, this happens only if someone is suspected to done serious crimes.
Using a Veracrypt hidden volume correctly and safely, is much more complicated than it seems. Please read the Veracrypt manual online and follow all of its precautions. It isn't just flash storage like SSDs and flash drives that could be a problem, it's forensic artifacts left behind on operating systems too. Either of those could give big clues that you actually have a hidden volume. That being said, I've never actually heard of a forensic lab proving someone was using a hidden volume.
As a cryptographer, if my threat model included needing a hidden volume, here's what I would do if I wanted to store a hidden volume on an SSD/flash drive:
1. Create and view a hidden container ONLY on a live operating system such as TAILS. This helps prevent forensic artifacts.
2. I would only use this to store data but I would not edit the file container once it's been placed on flash storage. Therefore there is only 1 non-changing file container on the flash storage device, preventing problems associated with editing it on such storage.
3. If you need to edit the container, you can't really. Instead, make an entirely new container on the live operating system with whatever changes to the data you need.
Read the documentation and think about if your threat model truly requires such precautions.