Regarding this, there are two key points:
1. Laravel sends the data to either POST or GET, other options query "emulated" (at least it was so, although in my opinion, this problem is not Laravel'I, and browsers that can submit the form only one of the two abovementioned queries)
2. If You have the files by any other method, except POST to convey it does not work, otherwise, the files mysteriously disappear.
Hence, we can conclude that the options requests other than GET/POST is made not more than for convenience, and in truth, the more it innovation Laravel developers in other frameworks such practices are not particularly well developed.
Such rules, which would read as follows on the query type depending on the number of changed fields - no, and on the server (in the target update data in DB) - the difference from what the request data was received either. In those days, when he designed and created the HTTP Protocol v1.0, on such a complex logic as change the type of query depending on the number changed in the form fields is not suspected (although I think of this before and now very few who would have guessed). Most of the requests are outside the scope of the GET and POST implemented for working with "resources" (read "files") via the HTTP Protocol and/or some lower-level tasks than just sending the form.
In Laravel, in some cases, it is convenient to use queries for example, type "DELETE" to remove some of the resource/records/stroking, as an alternative to a similar GET request with Postfix
/delete (as an example), it's a little offloads logic controllers and allows wider use of the system logic of routing, but no more.