Why some packages exist in package control but have icon removed?
I can’t install it, for example:
https://packagecontrol.io/packages/Toggl%20Timer
https://packagecontrol.io/packages/BufferScroll
https://packagecontrol.io/packages/Open-Include
https://packagecontrol.io/packages/SideBarFolders
https://packagecontrol.io/packages/SideBarGit
https://packagecontrol.io/packages/WordCount
https://packagecontrol.io/packages/BufferScroll
It means there was a package with that name at one point, but the package has been removed from the channel on purpose. Such packages are not listed in search or the browse pages. You can only find them via direct URLs or links from other sites.
Maybe he’s tired of supporting them. Maybe he doesn’t use those anymore so it doesn’t make sense for him to support them. You can fork them if you like. You could be the next maintainer as it is open source.
It takes time to support repos. Supporting repos is work. I know because I support a bunch. It is often a thankless job. People always want something, but often don’t want to put in effort to contribute (even if it’s just a simple donation). People don’t like to read the documentation and love to ask a question you’ve documented and answered hundreds of times. People don’t like to follow instructions you give them to get your support.
With that said, there are people who do contribute. And there are those who occasionally give thanks (sometimes verbally and sometimes with donations and sometimes with pull requests). Those are the people that usually give repo maintainers the motivation to keep supporting the project.
In short, sometimes it can just get tiring. And if you’ve moved on from your project (you don’t even use it yourself anymore), it might not make sense to keep supporting it. Only tito can answer exactly why. But I imagine he either doesn’t use them anymore and/or is tired of supporting so many repos.
@facelessuser this is also my first thought, that he removed the plugins from Package Control because he doesn’t have time to support / develop it. But his plugins are much popular, so he can just put the info that he doesn’t support / develop this plugin anymore - but not immediately removed it from Package Control, especially when some of his plugins are quite popular and a lot of people uses them 
Again, I don’t know his exact motivation behind his approach to discontinuing the support, but it is what it is. Yeah, it would have made sense to put out feelers first to see if someone was interested in picking up support, but everyone is different. Maybe he just didn’t want to deal with it anymore ¯\_(ツ)_/¯.