I think you’re still misdirecting your concern here. The limitation is only, and entirely, with your (former) web host.
Let’s Encrypt provides a Certificate Authority that issues certificates for free. That CA uses an open protocol which allows lots of people to develop software to automatically obtain and implement certificates. If you’re running your own server, especially on a Unix-like operating system, the odds are very high that you can use any of a dozen different pieces of software to obtain, implement, and renew certificates from Let’s Encrypt, and once you have it set up, it will renew automatically, pretty much forever.
The problem is that you aren’t running your own server. Instead, you have your websites hosted elsewhere. That means that your web host has control over a lot of issues, and you have much less control than if you were running your own server. A “good” (in this regard) web host will have a nice, pretty control panel, with a switch, knob, or checkbox to obtain a Let’s Encrypt cert–and there are many who do this at no additional cost. An “OK” web host will at least allow you to upload the appropriate certificate files–this can be a hassle, but it can still provide you with SSL for your site at no cost. But then there are “bad” web hosts, which charge a significant extra sum to do SSL at all. GoDaddy is one of these, it seems. There is literally nothing Let’s Encrypt can do to change this situation. You, and other (former) customers like you, are in the best position to effect change here, by leaving them for another host. If enough customers do this, hopefully they’ll realize that charging extra for baseline-level privacy and security is a bad business decision.