Hi
@Pupp1,
As far as I'm aware all the commercial loops are currently hybrid (HCL) so its necessary to enter carbs as you suspect.
There are variants of the DIY closed loops that are Fully Closed Loops (FCL) - I use a variant of AndroidAPS (AAPS) called Boost and use Libre 2, a Dana-i an android phone and (optional) a smartwatch for monitoring.
Boost monitors BG rising and then hits it with insulin - I only enter carbs for pizza, indian food and pasta (carbs spaced over 5 hours to warn the algorithm) I don't actually bolus.
To make this work properly you need an ultrafast insulin (Fiasp or Lyumjev) so it kicks in quicks enough.
There are other variants (have a look on the AAPS facebook user group
https://www.facebook.com/groups/AndroidAPSUsers) like AutoISF that are aimed at FCL (not used those though)
Boost works well for me - takes a lot to learn how to set it up - I'd recommend AAPS first to get it working correctly (could be used to simply declare carbs rather than bolusing for them in your situation) before moving to Boost.
This is a very technical solution - DIY means you need to compile the app and sideload it (so you are responsible rather than an off-the-shelf product which requires insurance and medical validation etc). So it will take a long time to get working, however the end point is I can now eat what I want (within reason) and it keeps me about 87%-95% TIR.
Might be a solution to investigate - there are other options on Apple - but don't know anything much about them - might be worth searing on DIY FCL and see what you get back.
hth