Should Git manage a single system as a single repository with a large number of sub-features?

I would like to ask for your advice on managing Git's repository.
Is there a good way to manage a single system program with 100 features in one system?
I am currently expecting the following two items.
(1) Manage all 100 functions in one repository
(2) Manage one feature at a time in a separate repository
(3) Others (I can't imagine it at all)

Until now, Subversion has managed functions 1 to 100 in a single repository.
There are about 20 developers, all of whom have access to all features 1 to 100.
We checked out only the features we needed at any time, and at that time we removed the features we didn't need from the local area.

With Git, the functions I need now are from 1 to 10, but I'm afraid that even unnecessary 11 to 100 are local, and I thought it would take a long time to pull.

However, I am not sure if I can manage as many as 100 repositories if I use a different repository.
It's not so realistic to create 100 directories each and clone each.
If you need 10 more features, I think it's a lot of work to pull 10 times.

In this case, how do you create and manage a repository?
Please lend us your wisdom.