Not telling your boss about changes you have pushed, that they specifically asked to be removed doesn't seem like a solution at all. It seems insubordinate at best. So you have to be careful in how you explain to your manager why that decision was made, and how it does introduce undo risk into the product.
The trick of course is avoiding that situation in the first place.
I think the root of your problem might rest in how you are presenting your problem to your boss. At the crux of it is that is sounds like you are asking a non-technical person to make a technical decision. That seems folly. I am going to assume that this non-technical person has a better grasp of the business context of the problem. If so, then that is what you need to focus on. Help your manager understand how each of your proposed solutions addresses the underlying business problem. Help them understand the time it will take to implement the solution, what that will mean to the schedule, and the benefits it might mean down the road.
Most often the solutions a developer needs to present are along the following vectors:
Here is a quick solution, that addresses the problem on its surface, will allow us to maintain our schedule, but will probably need to be completely reworked down the road.
Here is a solution that will take longer to implement, will mean we have to delay a launch, but will provide a better foundation for the product technically going forward.
If this is applicable in this situation, break it down for them in those ways. Make sure they understand the business and technical risks associated with the technically weaker solution as well. The technical details are actually somewhat irrelevant unless you make them relevant by making them the focus of your presentation to them. Instead, try to present your solutions through the lens of the business.
Finally, if the technical details are essential, then involve the lead developer in your presentation to the manager. Come in prepared and united. Practice what it is you want to say so that you are clear and concise. Bring in a 3-10 slide powerpoint presentation to help visualize your solution. Don't get bogged down in the weeds of presenting code, keep it high level, but sufficiently detailed to keep them informed. Make your recommendation and the rational behind it clear.