You have a deeper problem, that you are using 1 day a week to fix bugs. Kanban is about continuous flow. The team should be able to take in bugs and story work at the same time and your stakeholders should agree on what the priority of work is regardless of what day of the week it is. It sounds to me like the 1 day rule is a crutch that is preventing your stakeholders from learning how to negotiate priorities.
If you find the team consistently having bug work carry over the 1 day boundary, the team should be retrospecting on why and figuring out how to improve their process so that it better serves all the stakeholders on the team. Your WIP limit shouldn't change, if anything it might help to lower it if the team is struggling to have a cycle time of 1 day on defect cards. Or you need to be realistic and acknowledge that a 1 day cycle time is not the right thing to aim for.
The team should not be dropping work. Part of setting WIP limits and having the team stick to them is the discipline of getting something done done before moving to the next item. With all my kanban teams I strongly encourage team members to only move cards forwards once they are in progress. Cards that get blocked or are tempting for the team to move back to ready sit in-progress and hog up the team WIP limits. The team needs to have the discipline to work through their bottlenecks/blockers and achieve flow.