This is essentially the same as the answer above by @Mohammed Yaseen Ganai, but I felt that some more explanation was in order to really help you understand the suggestion.
The most important thing here is not breaking convention unnecessarily - there already exist UI elements to do exactly what you want to do: Radios and Checkboxes.
If you think you're asking your user too many questions, perhaps consider a way of getting the same info in fewer questions. I think if you ask your user for times, you can calculate where they are and how many times they eat implicitly. I would also have a "tabbed view" for "week day" and "weekend" (not everyone goes to work, but they all have weekdays and ...
I would definitely refrain from having the long products-input that stays empty. It is confusing and clutters the layout.
How about a vertical layout? This would allow you to get rid off the long empty Input field and the repeating labels. Once a product is selected the chip is added above the input field and the input field moves down to make room for the ...
Vertically below each other in an order that makes sense to your users.
The issue with putting fields horizontally next to each other is that they are sometimes missed.
Have a search for LukeW, he is a UX researcher at Google and has some amazing content on form best practices.
I think the blue section should appear automatically after filling the green and red ones.
in the context of IP and port, I think it is worth using validation (as for the ip format - is it 4 or 6?):
Inform the user about the correct or incorrect address based on the defined format (green and ...
Switches are generally used when there are only one or two options. In this case, there a four options so checkboxes would work better. The options could be made more user-friendly and understandable with the addition of a verb:
Allow multiple valid answers [checkbox]
Allow multiple attempts [checkbox]
Shuffle questions [checkbox]
Shuffle answers [...
Structurally your form should be a single column, nothing should be side by side. Also labels should always sit on top of the inputs, instead of next to them.
The reason behind this it is that we read left to right and then top to bottom, that is different in other parts of the world though.
Also make sure the spacing between the label and the ...
Allow only 1 to be locked at a time
Essentially make them radio buttons. It looks like the three variables (rise, run, grade/angle) are one of three things to the user:
I know this value
I'm trying to find out this value
I'm experimenting with this value
If any two of them are the first, allow the user to put them in directly (just have four number input ...