Unless you are replacing a 317 or need the additional ports, the 12S+ is a hard buy. I have two of each model, with one 12S+ in the field for Ubiquiti Wave AP's, and the other three in the lab for testing and projects.
Well I have 3x 317 and one 326 so it kinda became bottleneck to have one 10G uplink to CCR1009. Especially since all those 317 are interconnected with 40G LACP. 20G uplink of 16G would probably be sufficient for now but it seems to be less future-proof, it has noticeably lower CPU clocks and I don't think RM version would be happy with Noctua fans. I mean 12S+ is basically passive device with aux fans so they're not super critical and probably it'd survive even without them. 16G in rackmount version is not so I'll pass. I'm looking for more or less desktop device and passively cooled 16G is meh due to nerfed CPU so... unless there's some really good reason to avoid it, I guess I'll bite the bullet on 12S+. I'll probable connect it via 40G LACP to all those 317s to have 40G shared backbone across all 10G ports. I don't have a lot of 1G devices. Most of my home servers, hypervisors and workstations have at very least 2x10G bond with 9k jumbo across entire LAN with NVME Gen 4 RAID storage. That's one of main reasons to upgrade - CCR1009 is significantly underpowered comparing to end devices in this network.
I know 317 has L3HW but it only works on ROS 7 for fasttracked connections which is not applicable when you use L2 firewall on bridges and as of now - I do in some places. I hope CCR2004 will pull off 10G with 9k jumbo without fasttrack. Also I'm a bit afraid of migration to ROS 7 (which I haven't seen so far and I'm not sure if my config will properly migrate) so I'd prefer to not YOLO migrate to it on any of my existing, actively used devices. Hence getting CCR2004 sounds like good idea.
If you're getting 19G with 1500 mtu I guess it should reach about 40-50G with 9k jumbo - I was getting around 2x perf boost on CCR1009 just from moving to 9k. But then again I'll get penalty from not using fasttrack so we'll see...