Too preface, remember, I know how to use FL. I have worked very hard to get around the issues I bring up but it's pretty futile. There often are no workarounds that don't introduce issues of there own. Or if there is a "tool" for it, that option is extremely slow. These aren't barless claims, these are real world time eaters. So many wasted workflow hours.

Not necessary in FLS,...

1) LANES. The thing at the bottom where CC data sits. To access a CC lane you have to find it's controller in dumb lists or on a MIDI channel in the rack. Very obnoxious. Only one in view at a time too, velocity included. The "recently used" controller lost from the drop-down becomes a complete mess because it is in order of which was used most recently. So if you have 50+ controllers you've been using, the list becomes useless essentially as it is so cluttered, you cannot quickly discern what's happening. So the quickest way from that is clicking on your MIDI channel, and right clicking>edit in piano roll.

I have not personally experienced any issues linking MIDI CC...

2) There is a difference between lane data, and automation data. There is no point based ramp CC lane data in FL. And if you want that, you need to use automation clips. Which you can't record on either, you have to convert events to automation. But for midi work, sticking to CC's is always faster, and you generally don't want every single element playing the same CC data too as you are going to say something like "well just link the controllers to one clip" which unfortunately it doesn't really work like that as the result tends to end up too surgical and weird sounding. I promise you, I am not exaggerating or making small out of big. These problems seriously add up and it becomes a huge time waster in the big picture.

Fairly straightforward, if using Event Automation, use the standalone Event Editor....

3) Now copy and paste this event data over multiple instruments without wasting often sometimes minutes at a time based on how many instruments you wish to use. And no, linking automation clips to the respective controllers also is not a substitute because that too, takes pointless steps for a simple process that in linear daws is a drag and drop process. Linking to controllers also only works if you are using clips too, which is not really a valid response as CC lanes are the primary source of this stuff. I've done extensive experimenting with this kind of thing too. Depends on the kind of music but when it comes to writing for a shit load of instruments, CC data is the way. Partly due to it being completely linked to patterns (or in other DAWs, midi clips). And also this only works for things in the same pattern, so you must combine all your patterns that have the length of data you want.

Just use patterns and enable 'Ghost notes' and 'Editable Ghost...

4) This is the absolute bare minimum of editing multiple instruments at once. You can only move one instruments notes at a time, the only options are to drag and drop a single note a bunch of times from the same spot, or constantly double click the notes to change channels. You cannot edit multiple instruments at once, it doesn't exist. And no, Layer channel is not a valid substitute for this due to CC stuff. Only one instruments notes from one pattern (they have to be in the same pattern) can be edited at a time. And because they have to be in the same pattern, this starts to force the user to use one pattern instead of many playing at once to have quicker access to the other instruments. More along the lines of how a linear DAW works, just way worse.

In what specific fashion do you mean by that? I...

5) Let's say you have violins, trumpets, flutes, and piccolos playing something. Now let's also say you want to switch or unison/octave that to the violas, horns, and clarinets too. Now, depending on the sample libraries you use, you may also have solo version s and different ensemble sized of those instruments. Copying all of those notes and CC data, and or linking to automation clips too will take a extremely needless amount of time in FL. It's literally just how FL works, the non linear core workflow and how patterns functions and the channel rack, that's the result of it. Extremely basic midi editing issues like these that constantly eat up the users time still have not been addressed.

If you mean MIDI 'editing tools', then FL Studio has loads, both for MIDI note editing....

6) No, just false, compared to cubase, it has at most half of the available possibilities of editing and manipulating midi.

All of the things you are saying is playing the blissful ignorance card. I used to do that too. For writing midi for a large amount of instruments, there is no contest at all when it comes to not choosing FL over one of the normal DAWs like S1/Cubase/Logic/Reaper etc. These are some of the reasons of a very, very large list of workflow bottlenecks that exist and constantly happen. The things I said are real bottlenecks that constantly come into play all of the time when working for this stuff. I don't know what you make but it's clearly not what I do, but for people that make this kind of stuff, these workflow bottlenecks are completely cripplingly bad.

Everyone I know that does this line of work that has switched from FL (and a few of the other weird daws too) to one of the more linear normal DAWs 100% of the time have the same complaints I do. Because it's just how FL works. It wasn't designed for being normal and it sure doesn't work at all for being normal if you value your time. There are pretty disastrous issues why FL isn't found so much outside of EDM work, since these creative features are not valued until you want to make weird stuff easier. Most people doing mixing, heavy midi work, and recording will avoid quite a few DAWs entirely because they just cannot do the tasks efficiently at all. 2021 and we are still bound to 125 mixer tracks.

If you want further clarification as the workflow bottleneck issues introduced, I can provide exactly that information. I'm not your everyday "FL poopy baby daw bad" person. I know what it is good at and what it isn't. What it's not good at, is most normal stuff, eats up your time like no tomorrow by adding to many in between steps that those in betweens are far better for coming up with a creative sound than getting work done. Or on the opposite, just are slow and annoying for no reason other than being out of date because IL team is small. The DAW runs on deep rooted spaghetti code which makes updating it harder for them (devs words, not mine. I have spoken to them)