Hi @raghav,
Our great community members have stated it quite eloquently here: We believe HTTPS support should be "free" for everyone, and we encourage hosting providers to do that. But we don't require it as a condition of using Let's Encrypt. It would be too burdensome to enforce, and there may be some cases where it makes sense for a hosting provider to temporarily charge a little more for HTTPS support (for instance if their newer hosting plans cost more and they are using HTTPS as a "carrot" to get old customers to upgrade).
To be clear, when I say "free" I mean "no added cost," since most hosting plans cost money.
If a hosting plan costs $100/month without HTTPS, and and extra $10/month to add HTTPS, you should just treat that plan as if it costs $110 total. If someone else can offer similar service for $105, great. But if the overall service is cheaper than the alternatives, it may still be worthwhile for you, even if it feels unjust that the HTTPS support is treated as a separate line item.