Writing code that works isn't always the most important part. Writing easy to read will no only help you look back at your source code, but others who will.
You were probably introduced to loops to help make your life easier.
Lets say I wanted to print "Hello World" five times, I could
A)
System.out.println("Hello World");
System.out.println("Hello World");
System.out.println("Hello World");
System.out.println("Hello World");
System.out.println("Hello World");
B)
for(int i = 0; i < 5; i++) {
System.out.println("Hello World");
}
Which is easier to read? Imagine instead of 5, we wanted to do it 1,000x times. You can clearly see that loops help keep code clean.
Now, to your questions
1)Can anyone give me some insight as to what this means - referring to "destructures the code"
This is referring to keeping code clean. Your code should have easy to follow logic.
2)Furthermore, what are the drawbacks of "destructuring the code"?
The drawback to "destructuring" is poor code management and increased chance of bugs. When your code is not properly structured, others will have a hard time reading it and you will hate looking back at it in a few weeks.
The extensive usage of breaks will force readers of your code to scroll through the code and line up the correct loop that is being broken out of. Overly using it will cause confusion and essentially be mimicking "GoTo" statements.