The cause of the 10 streams allocated is caused by the client when the provider is not responding. In this case, no streaming traffic is happening, so a stream timeout is required to release the tuner. For internalproxy, it is set to 120 seconds. For steamlink, it is set to 59 seconds. Some clients reset the channel or go to a different channel, if data is not received in a short time. This causes the tuners to stack up. Many clients can be configured to change their responses to no data, but that is the reason. So, if you had waited with no channels active, the tuners would have timed out. Also, you can tell that the tuner is stagnate because the home page will list the tuner status as Starting or NoReply, which means no data has been received for a while.
As for the database, I use DB Browser for SQLite to edit the databases. It probably would not work in the long run unless you turned off the daddylive channel updates in the scheduler. Everytime the scheduler runs, it verifies no old channels need to be removed. Once you have the channel scheduler for daddylive cleared, then you can edit the database files all you like. The only piece that will be difficult to know is the Referer. You can guess it and see if it works. I believe you get a 503 type error, if the referer is incorrect.
